post

Most companies run on one spreadsheet nobody dares touch. We turn that into an application with permissions, an audit trail and a shape that survives the person who built it leaving.

What this looks like in practice

No two projects are identical, but the shape of the work is. Here is what the weeks actually contain.

We start with the smallest version that removes real work from someone's day, put it in front of them, and grow it from what they actually do with it.

  • Fast on a mid-range phone
  • Content structure and copy

12.000+

icon
  • Fast on a mid-range phone
people

The parts that decide the outcome

Everything else is detail. These two are what separate a site that works from one that merely exists.

icon

Decisions we can defend

icon

Decisions we can defend

What happens after launch

A website is not finished when it goes live; that is when it starts being used. We stay for that part.

After launch

icon

Built on boring, well-supported technology on purpose. Interesting frameworks are somebody else's maintenance problem in three years.

person

Frequently asked questions

A brochure site is typically six to eight weeks; a store or an application, three to five months. The variable is almost never our speed — it is how long content and approvals take on your side, which is why we agree those dates up front too.

Yes, entirely, from the first day. The repository is yours, the design files are yours, and there is no licence to renew. If you decide to work with someone else later, nothing has to be bought back.

That is the point of the CMS we build for you. Fields are named for what they are, previews match what publishes, and there is no way to break the layout by editing text. We train your team and leave written notes.

A maintenance plan if you want one: updates, monitoring, offsite backups, small changes included, and a short monthly note about what changed. If you would rather handle it in-house, we hand over documentation and answer questions for free for the first three months.

Often. Plenty of sites need their performance, accessibility or checkout fixed rather than a rebuild. We audit first and tell you honestly which of the two you are looking at, even when the answer is the cheaper one.