How we work
Five stages, one team, no surprises
From the first workshop to the hundredth update, here is how a project with us runs, what you see at each stage and what we ask of you.
A typical project
- Week 1: discovery workshop
- Weeks 2–4: design you can click
- Weeks 5–12: build in two-week sprints
- Week 13: launch and training
The five stages
Most first versions launch in ten to fourteen weeks.
- Discovery. A fixed-price half day with your team. We agree who the tool is for and what it must do at launch, and send a brief, first screens and a price range.
- Design. Lena turns the sketches into clickable screens. You try them on your own phone, show your staff and tell us what feels wrong before any code is written.
- Build. Two-week sprints. At the end of each one you get a test version on your phone and a short note: what is done, what is next and any decision we need from you.
- Launch. We submit to the app stores, set up your accounts in your name, train your staff and stay on call for a quiet first week.
- Support. A monthly plan keeps the app current and improving. Small changes ship every month; larger ones get a quote first.
What you see along the way
Every two weeks
A test version
A new build on your phone, with a note in plain English. No demos you cannot touch.
Every Thursday
A short check-in
Fifteen minutes by phone or video to answer questions and agree the next small decisions.
At any time
A shared board
Every task, open question and change request in one list you can read without logging into anything complicated.
Who does what
Small projects work when everyone knows their part.
| Stage | We do | You do | Usually takes |
|---|---|---|---|
| Discovery | Run the workshop, write the brief | Bring the people who do the work | Half a day, brief within a week |
| Design | Clickable screens and two rounds of changes | Test on your phone, gather staff feedback | Two to three weeks |
| Build | Code, test, send a test version every sprint | Try each version, answer questions | Six to ten weeks |
| Launch | Store submission, setup, staff training | Approve the store listing, brief your team | One to two weeks |
| Support | Updates, fixes and monthly improvements | Collect requests from staff and customers | Ongoing, monthly |
Questions about working with us
What if we want to change something halfway through?
We expect it. Small changes go into the next sprint; larger ones get a written price and a new date before we start on them.
Who owns the code and the accounts?
You do. App store accounts, hosting and the code repository are set up in your name from the start, with us added as helpers.
How much of our time will it take?
About half a day for the workshop, then roughly an hour a week to try test versions and answer questions.
Start with a free 30-minute project call
Tell us what you would like to build and we will tell you plainly how we would approach it.