Regular written updates
What we finished, what's next, and anything we need from you. Short, readable and easy to share with your team.
How we work
A clear process, from first call to hand-over.
You always know what we're building, what it costs and what comes next. Here's how an engagement runs.
The process
-
A free intro call
A 30-minute call about what you want to build, who it's for and what matters most. We ask questions, give you an honest view on approach and rough cost, and tell you if we're not the right fit.
-
A small paid pilot (optional, recommended)
About a week of real work on a small, useful piece of your project, for a fixed fee. You see our code, our communication and our pace before committing to more. If you continue, the pilot fee is credited against the project.
-
A written scope and price
For a project, we write down what we'll deliver, the milestones and a fixed price. For a dedicated engineer or team, we agree the roles and a monthly fee. No surprises later.
-
Development, with regular updates
We build in short cycles. You get regular written progress updates and demos at key milestones, so you can see the product take shape and change direction early if you need to.
-
Full working demo and hand-over
At the end of the project we walk you through a full working demo, then hand over the code, documentation and access. After that, ongoing support is available if you want it.
Communication
Good software depends on good communication. We make it easy to know where things stand.
A shared channel
We join your Slack or Microsoft Teams, so questions get answered in the same place you already work.
Calls when they help
Kick-offs, milestone demos and decisions are easier on a call. We book them when they're useful, not by habit.
Hours that fit yours
We work flexible hours that overlap with your working day, wherever you are.
Quality
Quality is part of the work, not an extra you pay for.
Code reviews
Every change is reviewed by another engineer before it's merged.
Automated tests
We write tests for the parts that matter as we go, so new work doesn't break old work.
CI/CD
Tests and checks run on every change, and deployments are automated and repeatable.
Documentation
Setup guides, architecture notes and decisions are written down, so anyone can pick up the code.
Security and IP
Your product, your code and your data stay yours.
NDA from day one. We sign your NDA, or ours, before you share anything confidential.
IP assignment. Our contract assigns the intellectual property in the work to you.
Your repositories. The code lives in your GitHub, GitLab or Bitbucket from the first commit.
Your cloud account. Infrastructure runs in accounts you own and control.
Least-privilege access. We ask only for the access a task needs, and you can remove it at any time.
Engagement models compared
| Model | Best for | How pricing works | Commitment | You get |
|---|---|---|---|---|
| Fixed-price project | A product or feature with a clear goal, such as an MVP | A fixed price for a written scope, paid per milestone | The agreed scope, one milestone at a time | A working product, a full demo and a hand-over |
| Dedicated engineer | Ongoing work on a product you already run | A monthly fee per full-time engineer | Month to month, with 30 days' notice | An engineer in your tools, standups and process |
| White-label | Agencies that need extra delivery capacity | Per project or monthly capacity, custom quote | Per project, or monthly capacity | Work delivered under your brand and your client agreements |
Want to see how this would work for you?
Book a free call and we'll walk through your project step by step.