01
Fixed-scope project
A defined outcome, a fixed price and a timeline agreed upfront.
- Price agreed before work starts
- Milestones with clear deliverables
- Ideal for a first collaboration
Best forMVPs, websites, well-defined features
A process designed to take the risk out of software projects.
Clear phases, a demo every week, quality checks on every change and a clean handover. Here is exactly what working with us looks like.
How we work
Five phases, no surprises
Five phases, each with something concrete you can review before we move on.
-
Discover
We map goals, users and constraints, and agree on the smallest version worth building.
- What happens
- Workshops with you and your team to understand the business goal, the users and the constraints: technical, legal and budget.
- What you get
- A written scope, an estimate, a plan and the main risks, in plain language.
- Your involvement
- Two or three working sessions and access to the right people.
-
Design
Architecture, data model and interface prototypes, validated with you before any code.
- What happens
- We design the architecture and data model, and prototype the key screens so you can click through them before we build.
- What you get
- A clickable prototype and a short technical design document.
- Your involvement
- Feedback on the prototype; one decision-maker to sign it off.
-
Build
Short iterations, a working demo every week, tests and code review on every change.
- What happens
- We build in one- or two-week iterations. Every change is reviewed and tested, and lands on a staging environment you can use.
- What you get
- A weekly demo, a short written update and steady progress you can see.
- Your involvement
- About an hour a week: the demo and quick answers to our questions.
-
Launch
Production hardening, monitoring, a security review and a calm go-live.
- What happens
- Load and security checks, monitoring and alerting, backups and a rollback plan. Then a planned, rehearsed release.
- What you get
- Your product live in production, plus a runbook explaining how to operate it.
- Your involvement
- A go/no-go decision and, if useful, a short training session.
-
Evolve
We keep improving it with you, or hand it over to your team with full documentation.
- What happens
- We measure how the product is used and plan the next iterations, or prepare a complete handover to your own engineers.
- What you get
- A prioritised roadmap, or a handover with documentation, access and a walkthrough.
- Your involvement
- Whatever fits: ongoing collaboration or full ownership.
Every week
The rhythm of a project
Weekly demo
Thirty minutes, working software on screen, decisions made together.
Written update
What shipped, what is next, what is blocked, in five lines.
Shared board
Every task visible to you, in your tool or ours.
Direct chat
A shared Slack or Teams channel with the engineers themselves.
export const engagement = {
team: "dedicated", // senior-led, one point of contact
demos: "weekly", // working software, every week
ownership: "client", // your repo, your cloud, your IP
quality: ["tests", "CI", "review", "WCAG 2.2 AA"],
handover: { docs: true, runbook: true, lockIn: false }, // no lock-in, ever
} as const;Engineering standards
Quality that is built in, not inspected in.
- 01
Code review on every change
No line reaches production without a second pair of senior eyes.
- 02
Automated tests & CI
Tests run on every commit; a red build never ships.
- 03
Security by default
OWASP Top 10 practices, least-privilege access and secrets kept out of code.
- 04
Accessibility
Interfaces built to WCAG 2.2 AA: contrast, keyboard use and screen readers.
- 05
Performance budgets
Core Web Vitals and response times tracked, not hoped for.
- 06
Documentation & runbooks
Written for the next engineer, who might be on your team.
Security & ownership
Your code, your data, your IP.
- We sign your NDA (or ours) before you share any detail.
- Intellectual property is assigned to you in the contract.
- Code lives in your repositories and runs in your cloud accounts.
- Access is personal, least-privilege and removed at the end of the project.
- We follow the GDPR and can sign a data processing agreement.
- No lock-in: everything we build can be run without us.
Ways to work together
Ways to work together
Every engagement starts with a free 30-minute call and a written proposal. No commitment before that.
02
Dedicated team
A dedicated team of our engineers working as an extension of yours, billed monthly and scalable as you grow.
- Monthly rate, no long lock-in
- Priorities set by you, every week
- Scale the team up or down as needed
Best forProducts in active development
03
Audit & advisory
A short, focused review of your architecture, code, cloud costs or AI strategy.
- Fixed duration and price
- Written report with prioritised actions
- Debrief call with your team
Best forSecond opinions and technical due diligence
Questions
Frequently asked questions
How much does a project cost?
It depends on scope, so we never quote blind. After a discovery call we send a detailed proposal with either a fixed price or a monthly rate, a timeline and exactly what is included.
How long does a project take?
A focused website or prototype usually takes a few weeks; a SaaS first version or a complex platform takes a few months. Whatever the size, you see working software within the first weeks.
Who will work on my project?
A dedicated team of experienced engineers, led by a project lead who is your single point of contact from kick-off to launch. We do not subcontract your project.
How do you guarantee quality?
Through process: code review on every change, automated tests, weekly demos and clear milestones. You see progress every week, the code is in your repository from day one, and you can stop at any milestone keeping everything built so far.
Do you sign NDAs?
Yes. We can sign your NDA, or send ours, before you share any confidential detail.
Who owns the code and intellectual property?
You do. IP is assigned to you in the contract, the code lives in your repositories and the infrastructure runs in your accounts.
Can you work with our existing team or codebase?
Yes. We start with a short code and architecture review, then work inside your tools, workflows and conventions.
Which time zones and languages do you work in?
We work remotely with clients around the world and plan calls to overlap with your working hours, whether you are in Europe, the Middle East, Africa or the Americas. We work in English, French and Arabic.
What happens after launch?
Your choice. We can stay on for maintenance and new features, or hand everything over to your team with documentation, a runbook and a walkthrough.
How does payment work?
Fixed-scope projects are usually invoiced by milestone; dedicated teams monthly. The exact terms are set out in each proposal before anything starts.
Contact
Let's talk about your project.
Tell us what you are building. Our team reviews every request and replies within one business day, with questions, not a sales script.