Know how this goes before you sign

Agencies are usually vague about process until the contract is signed. Here is ours in full: how we run projects, what lands in your inbox, how often we meet, and how long it takes.

The idea

Predictable beats impressive

Most of what goes wrong on a web project is not technical. It is a surprise: a scope change nobody wrote down, a review that arrived three weeks late, an invoice for something you thought was included.

Our process is built to remove those. Work is visible on a shared board, decisions get written down where you can find them, and the price is agreed before anyone opens an editor.

Dig in

The four things people ask about

Each of these has its own page. Read the one you care about and skip the rest.

Process

Methodology

How a project actually runs, from the first conversation through discovery, build, launch, and the ongoing work afterward. Includes how we handle scope changes and disagreements.

Output

Deliverables

What you receive and get to keep. Code, design files, documentation, training, and access credentials that are yours whether or not you stay with us.

Rhythm

Meetings

How often we meet, who needs to be there, and what we cover. Short, regular, and cancellable when there is nothing to decide.

Pace

Timeline

Realistic ranges for the work we do most, and the things on your side that usually decide whether a project lands early or late.

Getting started

What the first ninety days look like

Every engagement is different, but the opening moves rarely are.

Week 0

A free consultation

Thirty minutes with the people who would do the work. You describe what is wrong, we tell you what we would do about it and roughly what it costs. No deck, no follow-up sequence.

Weeks 1-2

Access, audit, and a first backlog

We get into your systems, review what is there, and turn everything you have been meaning to fix into a prioritized board you can see. You approve the order before we start.

Weeks 3-6

The first shipped work

We deliberately start with things you will notice: the broken form, the slow page, the accessibility problem that has been sitting there. Early wins build the trust the harder work needs.

Weeks 7-12

The bigger initiative gets underway

By now we know your systems well enough to take on the refresh, the integration, or the rebuild. It runs alongside the steady maintenance rather than replacing it.

Ongoing

A rhythm you stop thinking about

Two-week cycles, a working session at the end of each, and reserved capacity for whatever the month throws at you. Most clients stay here for years.

Common questions

Honest answers to the questions we get most

What does a two-week sprint with you include?

A sprint starts with a shared backlog and an agreed set of priorities. Most of it is roadmap work: new pages, features, and fixes you asked for. We also hold back capacity for the things that show up mid-sprint, like an urgent press release or a same-day fix. At the end of every sprint you see what shipped, what is next, and what is blocked.

What do you need from us to get started?
Usually, admin-level access. That surprises people, but most platforms require admin permissions to generate API keys, configure OAuth credentials, or set up webhook endpoints. We'll walk you through exactly what we need and why before we ask for access to anything.
What happens after launch?
A thirty-day stabilization period comes with every build. After that, most applications need ongoing care: new features, bug fixes, integrations as new tools come up, and occasional dependency updates to keep everything secure. We typically transition into a retainer sized to match the application's complexity and how often things change.
Do you work with our existing design or branding agency?

Often, yes. On several engagements the design direction comes from a partner agency and we handle the development that brings it to life. The pattern that works: they deliver comps, we build to them, they sign off. We are happy to sit in the same threads and keep the handoff clean.

Can my team update the site after launch?
Yes. We build on a CMS your team can manage, and structure the design so new pages can reuse what already exists.
Let's talk

Want to see how this would run for you?

The consultation is the first step of the process above, and it is free. Bring the work you have been putting off and we will sketch out the first ninety days.

Book a free consultation