How we work
Working software, every two weeks.
A clear process, senior people and honest updates. Here is exactly how we take your product from the first call to launch, and beyond.
Every engagement includes
- Senior engineers leading your project
- Working software every two weeks
- Weekly written progress updates
- Your code and IP from day one
- NDA before detailed discussions
01Process
From first call to launch.
Five phases, one senior team. You always know what is happening, what comes next and what we need from you.
- 01
Discover
Typically 1–3 weeks
We map your goals, users and constraints, then define what success looks like in numbers.
What happens
- Workshops with your stakeholders and users
- Audit of existing systems, data and constraints
- Success metrics, priorities and risks agreed
You get
- Stakeholder workshops
- Technical audit
- Scope & roadmap
Your part
Share your goals, context and access to the people who know the problem.
- 02
Design
Typically 2–4 weeks
Architecture and experience are designed together, so the product is beautiful and buildable.
What happens
- User flows and clickable prototypes
- A design system built for your brand
- Architecture and technology choices documented
You get
- UX flows & prototypes
- Design system
- Solution architecture
Your part
Review prototypes and give feedback; we test key flows with real users.
- 03
Build
Two-week sprints
Senior engineers ship in short, demo-able sprints with automated testing from day one.
What happens
- Features built, reviewed and tested every sprint
- A demo of working software at the end of each sprint
- Automated tests and deployments from day one
You get
- Two-week sprints
- CI/CD pipelines
- Code review & QA
Your part
Join the sprint demos, set priorities and accept finished work.
- 04
Launch
Typically 1–2 weeks
Hardened, monitored and documented: we go live with a rollout plan, not a leap of faith.
What happens
- Performance, security and accessibility checks
- Monitoring, alerts and a rollback plan
- Go-live runbook and team handover
You get
- Performance & security checks
- Observability
- Go-live runbook
Your part
Approve the launch plan and prepare your team and customers.
- 05
Grow
Ongoing
SEO, paid acquisition and product analytics compound the value of what we built together.
What happens
- SEO, Google Ads and conversion experiments
- Product analytics and roadmap reviews
- Support and maintenance with agreed response times
You get
- SEO & Google Ads
- Conversion experiments
- SLA support
Your part
Review results with us and decide what to improve next.
02Engagement models
Choose how we work together.
Not sure which fits? Many clients start with a short paid discovery phase, and we recommend a model from there.
- 01
Fixed-scope project
MVPs and features with a clear, stable scope.
- Pricing
- Price and timeline agreed upfront, after discovery.
- How it works
- Changes go through a quick change request, so budget stays predictable.
- 02
Agile product team
Evolving products where priorities change often.
- Pricing
- Monthly billing for the time actually spent (time and materials).
- How it works
- Re-prioritise every sprint without change requests.
- 03
Dedicated team
Long-term products that need a stable, full-time team.
- Pricing
- A flat monthly fee per team member.
- How it works
- The team works in your tools and rituals, with our delivery lead.
- 04
Staff augmentation
Filling specific skill gaps in your own team.
- Pricing
- A monthly rate per specialist.
- How it works
- You manage day to day; we handle hiring, HR and replacements.
| Compare | Fixed-scope project | Agile product team | Dedicated team | Staff augmentation |
|---|---|---|---|---|
| Budget predictability | High | Medium | High | High |
| Flexibility to change | Low | High | High | High |
| Your management effort | Low | Medium | Medium | High |
| Typical length | 1–6 months | 3+ months | 6+ months | Flexible |
03Communication
Updates you never have to chase.
Clear, predictable touchpoints, in the tools your team already uses.
Every day
- Async progress updates in your Slack or Teams
- Direct access to the team
Every week
- Written status report: progress, risks, next steps
- Budget and timeline tracking
Every two weeks
- Sprint demo of working software
- Planning and backlog review
- Retrospective
Every quarter
- Roadmap and outcome review
- Architecture and security health check
We work in your tools
- Slack or Microsoft Teams
- Jira or Linear
- GitHub or GitLab
- Figma
- Notion or Confluence
- Google Meet or Zoom
04Quality
Our definition of done.
Every release meets the same bar, whatever the size of the project.
Code review on every change
A second senior engineer reviews every change before it is merged.
Automated tests and CI/CD
Tests run on every change, and releases are automated and repeatable.
Security checks
OWASP Top 10 practices, dependency scanning and safe secrets management.
Accessible by default
Interfaces built to WCAG 2.2 AA, so everyone can use your product.
Fast by design
Performance budgets and Core Web Vitals checks before every release.
Documented and handed over
Architecture notes and runbooks, so your team is never locked in.
05 · Ownership & security
Your product. Your code. Your IP.
Read how we handle personal data in our Privacy Policy.
- Your repositories from day oneCode lives in your GitHub or GitLab, not ours.
- You own the IPCode, designs and documentation belong to you, in writing.
- Confidential by defaultNDA before detailed discussions, least-privilege access for every engineer.
- No lock-inDocumentation and a proper handover whenever you want to take over.
06FAQ
Working together.
After a discovery call we break the work into features, estimate each one and share a range with the assumptions behind it. For a well-defined scope we can fix the price; for an evolving product we agree a monthly budget.