Question 1

Do I have to take this after a build?

Accepted Answer

No, and plenty of people don't. Everything gets handed over in a state where you can run it yourself, and the recorded walkthrough exists so the person who has to use it has seen it explained once. Care is for when you'd rather that person wasn't you. If you want to try running it yourself first and start this later, that's a completely normal thing to do and it costs you nothing to wait.

Question 2

What's the difference between this and just keeping the site online?

Accepted Answer

Keeping it online is hosting: the certificate stays valid, the domain doesn't lapse, and somebody answers if it goes down. That's the floor and every live site has that cost, whoever provides it. Care is the layer above: someone actually looking at the thing every month, testing the booking flow rather than assuming it works, and doing up to two hours of real changes. Roughly one to nine in cost, so it's a step rather than a slope, and you can take the floor on its own indefinitely.

Question 3

What actually happens in a normal month?

Accepted Answer

Most months, not much, and that's the point of paying for it. I check the site's up and the main path still works end to end, submit the form myself to confirm it lands, look at the domain and certificate dates, confirm analytics is still collecting, and sweep for broken links and anything obviously wrong. Then whatever small updates you've sent go in. You get a plain summary of what I found and what I changed, in English, not a dashboard export.

Question 4

What if I need more than two hours in a month?

Accepted Answer

You'll hear about it before the time runs out, not after. Small overruns I absorb, because tracking a business to the minute is a worse relationship than eating fifteen minutes. Anything genuinely bigger gets quoted as its own piece of work with a number on it before I start, so there's never a surprise invoice. If it's happening every month, the honest answer is that your monthly is priced wrong and we should change it rather than pretend.

Question 5

Why won't you look after a site somebody else built?

Accepted Answer

Because I'd be guaranteeing a response time on something I can't see inside. Sites built elsewhere carry decisions I didn't make, on platforms I might not have access to, with things wired up in ways that only become visible when they break. Agreeing to a monthly fee before knowing any of that would mean either padding the price for everyone or letting you down the first time something real goes wrong. So it's an onboarding audit first, priced once I know what's there, and then a straight yes or no. Sometimes the answer is no and you get the audit findings anyway.

Question 6

Do I own it after you build it?

Accepted Answer

Yes, all of it, on delivery. Source code, design files, content, images, domains, and any accounts or automations built as part of the work. Everything gets built inside platforms you already own and control, under your logins, not inside a Seal & Co. product. There's no buyout, no license fee, and nothing that expires if we stop working together. If you want to bring it in-house or hand it to someone else next year, you take the whole thing and nothing breaks. Worth asking anyone you're considering, because most agencies build you into their software and that's a retention plan rather than an asset.

We only look after what we built.

What actually gets done.

What that time is for.

$450 a month.

The usual questions.

Built by us? Then this is a short conversation.