How we work
From first call to running software, in four steps.
When we build something or advise you, you always know what is being done, who is doing it and what comes next. Here is what each step looks like.
- 01
Call
30 minutes to understand what you need, the constraint and the deadline. You get an honest yes, no or not yet.
- Held in French or English
- We ask about the system, the constraint and the deadline
- You leave knowing whether we are the right team, and why
- 02
Scope and people
A written scope, a fixed first milestone and the named people who will do the work, in-house and freelance.
- A written scope with a fixed first milestone
- The named engineers, introduced before work starts
- A plan you see before committing to a larger budget
- 03
Build in the open
Weekly demos, shared repository and tickets, decisions written down. You see progress, not status reports.
- Weekly demos of working software
- Shared repository and tickets you can follow
- Decisions and scope changes written down as they happen
- 04
Hand over
Documentation, runbooks and a walkthrough with your team. You own the code and can run it without us.
- Documentation and runbooks for what we built
- A walkthrough with the people who will run it
- Code, infrastructure and access in your accounts
One team, one contract, one company accountable
We staff each project with the engineers it needs, from our in-house team and our network of vetted freelance specialists. You deal with one company, not a group of suppliers.
In-house engineers
Our own engineers carry the project's continuity, standards and delivery oversight.
Vetted freelance specialists
Specialists chosen for your stack after we review their work history and technical fit. You meet them before they start.
One accountable contract
SDK Enterprises is the contracting party for the whole team and stays accountable for delivery.
Quality is how we work, every week
- Every change is reviewed by another engineer before it merges
- Architecture and scope decisions are written down with their trade-offs
- Critical paths get tests before we change them
- We follow your security standards, access controls and review processes
- Weekly demos show working software, not slides
- Risks and scope changes are raised when we find them, with options
What you get at handover
- Code in your repositories and infrastructure in your cloud accounts
- Documentation and runbooks your team can follow
- A walkthrough with the people who will run the system
- Written decisions, so the next engineer knows why, not only what
Tell us what you need.
Something to build, people to find or a question to answer. In a 30-minute call we listen and tell you honestly how we can help, and what it would take.