How we work

What actually happens, and when

Five stages from the first message to the month after launch, each with a date attached. If something here is not what you want, that is worth knowing before you enquire rather than after.

Five stages, start to finish

Each stage has a time against it, because a date you can plan around is worth more than a reassurance. If one is going to slip, you hear it in that week update rather than afterwards.

1

You get in touch

A confirmation arrives at once, and says it is automatic. Then a person reads it and replies, inside one business day. Not a sequence, and not a calendar link instead of an answer.

2

A call, then a quote

Thirty minutes to work out what you need and whether we are the right people. A written quote follows within three business days: fixed price, one page, what is not included stated as plainly as what is.

3

You sign, we send the questions

A short form that asks what we need to build the thing. About twenty minutes, saves as you go, and only the questions that apply to you appear. Kickoff is within five business days of signing.

4

We build, you review

An update every week on the same day, agreed at kickoff, so you know when to expect it. You review on a real URL rather than a flat image, with two rounds of changes included.

5

Launch, and after

We handle the domain, the certificates and the redirects. You are told when it is live rather than discovering it. A check-in after a week, then monthly.

The detail

The parts people ask about twice

The stages above are the shape. These are the specifics that decide whether a project runs smoothly, and they are the ones worth reading before you sign rather than after.

Almost all of it arrives in one place: the questions after signing. That step is the one that decides the timeline, because a build waiting on answers is the commonest reason a project runs late. Everything else is a reply to an update, which takes a minute.

Questions people ask once they are serious

That is the whole process. Nothing else appears later.

Start at stage one with a paragraph about what you are trying to build, or skip to the call and we will do the reading beforehand.

Book the call