CM AppsSubcontractor: build and deliver
You win the work,
we build it with you.
Subcontracted development for software companies, agencies, system integrators and consultancies. The contract with the client stays yours; we add the capacity, the expertise and the delivery.
DELIVERY CHAINYour client You
Scope, delivery and invoice
We stay behind the chain; your client sees you.
WHO IT IS FORYou have the work,
You have the work,
you need the capacity.
- Software companies and agenciesYou need a team to build all of the work you sold, or one module of it.
- System integratorsHardware, installation and field work are yours; the software layer needs a technical partner.
- ConsultanciesYou run the analysis and the client relationship and need someone to build the solution.
- Corporate IT teamsYour in-house team is busy with current work and the new project needs a separate delivery track.
WORKING MODELSFour setups,
Four setups,
by contract.
Subcontracted development
The contract sits between you and your client; we build as your subcontractor. You remain the single point of contact.
White-label delivery
Our name does not appear in what we deliver: repository, documentation and interface carry your brand.
Team extension
Developers who work alongside your team, inside your sprint rhythm and your tooling.
Fixed-scope delivery
A package with the scope written down and acceptance criteria defined up front.
HOW IT RUNSFrom takeover
From takeover
to handover.
- 01
Scope and confidentiality
An NDA is signed and the technical scope and acceptance criteria are written down. You do not have to disclose your client’s name.
- 02
Technical takeover
Existing code, data and infrastructure are reviewed; risks and gaps are reported back to you in writing.
- 03
Development and reporting
We work inside your project tooling; progress, blockers and remaining work are reported in a form you can show your client.
- 04
Delivery and handover
Source code, documentation, deployment setup and knowledge transfer. A warranty and maintenance window can be added to the contract.
BOUNDARIES AND COMMITMENTSYour client
Your client
stays your client.
- We do not contact your client directlyRequests, approvals and delivery run through you; anything else is agreed in writing beforehand.
- IP and source code are yoursRights to the code transfer to you on delivery; if any component stays with us, that is written down from the start.
- No name-droppingWe do not add the work to our reference list and do not discuss it with anyone without your permission.
- We work in your toolsRepository, issue tracking and communication can stay on your side; if needed we work from an address on your domain.
IN THE FIRST CALLLet’s pin down
Let’s pin down
the scope first.
Writing scope without knowing what you promised your client does not work. We start from these questions and build a realistic plan.
- 01
What delivery and what date did you promise your client?
- 02
Do we take the whole build, or one module?
- 03
Is there an existing codebase to take over?
- 04
Should the delivery appear under your brand?
QUESTIONS ON YOUR MIND
Before we start.
Will you contact our client?+
No. By default everything runs through you. If a joint meeting is needed we join as part of your team — that is your call.
Does your name appear in the delivery?+
Not in white-label delivery. The repository, the documentation and the interface carry your brand.
Who owns the code?+
You do, on delivery. Licences of the open-source components and the terms of any prebuilt components of ours are written into the contract — no surprises.
How does pricing work?+
Fixed price where the scope is fixed, time and materials where it is open. Which one fits depends on how much is unknown; we decide together in the first call.
We have an urgent delivery — can you take it over?+
On takeovers we review the current state first and report the risks in writing. We do not say yes to a date we do not believe in; a missed delivery lands on both our names.
NEXT STEPTell us about your business.
Let’s talk about your project