How we work
How a project runs, start to finish
You agree the scope and price before we start, see working software every week, and own everything we build. Here's how a project runs.
The four steps
Step 1 · 1 to 2 weeks
Discover
We learn your business, users and goals, then agree on scope, budget and what success looks like, in writing.
What you get
- Project brief and success measures
- Scope with a fixed quote or estimate
- Technical approach
- Timeline with milestones
Step 2 · 1 to 4 weeks
Design
We map the user journeys and design the interface, and you sign off on a clickable prototype before production code starts.
What you get
- Sitemap and user flows
- Wireframes
- High-fidelity designs
- Clickable prototype
Step 3 · 3 to 12 weeks
Build
We build in short cycles and give you a live preview link from the first week, so you can watch the software take shape.
What you get
- Weekly demos
- A staging environment
- Automated tests
- Code in a repository you own
Step 4 · Ongoing
Launch and support
We handle the launch, monitoring and handover, then stay on to host, support and improve what we built if you want us to.
What you get
- Launch checklist and go-live
- Documentation and training
- Monitoring and backups
- Support and hosting options
Communication
You always know where your project stands
A weekly demo
A short call every week to show working software, answer questions and agree what's next.
A live preview link
From the first week of the build, you can click through the latest version whenever you like.
A shared channel
Ask anything in Slack, Teams or email. We reply within one business day, usually much sooner.
A written status report
A plain-English summary of progress, budget and risks.
Our standards
What you can hold us to
We put these in every proposal we send.
You own everything
The code, designs and intellectual property are yours. Everything lives in accounts you control.
Fast by default
We build to pass Core Web Vitals, because speed affects both search rankings and conversion.
Accessible from the start
We design and test to WCAG 2.2 AA, so people who rely on a keyboard or screen reader can use your product. It also lowers your legal risk.
Secure from day one
Least-privilege access, encrypted data, dependency updates and a security review before every launch.
Documentation included
Readable code, setup guides and runbooks, so any competent team could pick up where we left off.
Quick replies
You get a reply within one business day, and a named person who knows your project.
How involved do we need to be?
Expect a kickoff workshop, a 30-minute weekly demo and quick answers to questions as they come up. A single decision-maker on your side keeps everything moving.
What if our requirements change during the project?
They usually do, and that's fine. We discuss each change and quote it if it affects scope. Then you decide whether to add it now, swap it for something else or save it for a later phase.
Do you sign NDAs?
Yes. We're happy to sign a mutual NDA before you share anything confidential.
What happens if you miss a deadline?
We plan with realistic buffers and flag risks early in the weekly report. On fixed-scope work, extra time caused by our own estimates is at our cost, not yours.
Can we take the project in-house after launch?
Yes. You own the code and all accounts from day one, and we hand over documentation and a walkthrough so your team can take it from there.
Have a project in mind?
Book a free 30-minute call. We'll talk through what you need, tell you what we'd do and follow up with a written estimate. Prefer email? We reply within one business day.