How a project runs. Five steps, no surprises.
Every project, from a single website to a platform, follows the same path. You always know what we are doing this week and what you will have at the end of it.
- Step 1
Talk
A free first call.
You tell us what is getting in the way. We ask about the tools you use today, who will use the new thing, and what done looks like. If we are not the right team, we say so and point you to someone who is.
What you have at the endAn honest read on the problem, and whether we should work on it together. - Step 2
Scope
One page, written down.
We write a one-page brief: the problem, what is in, what is out, and the launch note we expect to send when it ships. Then a quote you can plan around, as a fixed project or a monthly plan.
What you have at the endA brief and a written quote. - Step 3
Design
Real screens with your data.
We design the screens people will actually use, with your menus, stores and numbers in them rather than placeholder text. You click through a prototype before anything is built.
What you have at the endA clickable prototype you can put in front of your team. - Step 4
Build
Something new to try every week.
The people who designed it build it. Each week there is a working version on a private link, and a short note on what changed and what is next.
What you have at the endWorking software, a little more of it every week. - Step 5
Launch and look after
Go live, then stay close.
We launch on our hosting or yours, watch it closely for the first weeks, and train the people who use it. After that, a care plan keeps it updated, monitored and improving.
What you have at the endA live product, notes on how it works, and a team that still answers the phone.
A normal week
Once the build starts, the rhythm stays the same until launch.
- Monday
A short note: what shipped last week, what is next, anything we need from you.
- Midweek
A working version on a private link. Click around, leave comments where they apply.
- Friday
Decisions written down, so nobody has to remember what was said on a call.
What we need from you
Projects slow down when these are missing, so we ask on day one.
- One person who can answer questions within a couple of days.
- Access to the systems we are joining, or an introduction to whoever runs them.
- Real content early: menus, prices, store lists, the spreadsheet everybody uses.
- Twenty minutes a week to look at the work and say what is wrong with it.
One team for the whole job. From the first sketch to the server it runs on.
The people you meet do the work.
No account managers in between. The person on the first call designs the screens, writes the code or runs the servers, and is still there next year.
We host what we build.
Sites and apps run on our servers with a standby ready, checked every minute. When something needs attention, we usually know before you do.
Everything in writing.
A one-page brief before we start, a written quote, and a short note every week on what changed. No guessing where the project is.
Ready for step one?
The first call is free. Tell us what is in the way, and we will tell you honestly what we would do about it.