Delivery capacity under your name
We build software for agencies who sell it and do not want to employ engineers. Your client never hears our name, the IP transfers to you on delivery, and you keep the relationship.
What we take on
Whole builds or specific parts of them. Most agencies come to us for the engineering and keep strategy, design and the client relationship themselves, which is usually the right split.
- Full builds from an agreed specification
- Backend and API work behind a front end your team designed
- Taking over a stalled project from another supplier
- Overflow capacity when your own team is committed
- Ongoing maintenance on something we or someone else built
How we stay invisible
Invisibility is operational, not a promise. It is built into how the work is set up, and every item below is standard rather than something you have to ask for.
- We work inside repositories and cloud accounts in your name or your client's
- No Recilens branding in code comments, commit messages, documentation or UI
- Commits authored under an address you nominate
- We never contact your client, and we decline if they contact us directly
- Documentation written in your voice, ready to pass on unedited
- We do not list your clients as ours, or use the work in our portfolio without written permission
NDA and intellectual property
A mutual NDA is signed before any client detail is discussed, not after a proposal. All intellectual property in the delivered work transfers to you on final payment, including source, schema, deployment configuration and documentation. We retain no licence and no right to reuse client-specific work. Generic internal tooling we bring to the project stays ours, and anything of that kind is listed in the agreement so there is no ambiguity later.
Service levels
These are the commitments in the agreement, by tier. They are deliberately modest and met, rather than ambitious and missed.
- Scoping response: five working days registered, two active, one strategic
- Progress build to staging every two weeks, without exception
- Defect in delivered work: acknowledged within one working day, fixed at our cost
- Escalation path with a named second contact if the first is unavailable
- Thirty days notice before any change to rates or capacity
How we communicate
One shared channel, one named contact on each side, and a fortnightly call while a project runs. We write to you, you write to your client. Nothing goes to your client from us, including automated notifications, which are configured to your address.
- A private Slack or Teams channel, hosted by you
- A named engineer contact, plus a named backup
- Fortnightly call, with written notes the same day
- A staging URL with basic auth, branded neutrally
How a project starts
You send a brief, we scope it in writing within the response time for your tier, you add your margin and quote your client. Nothing starts until you confirm. If the brief is thin we will say what is missing rather than guess and price the risk in.
Questions we get asked
That is your call and your relationship. Many agencies say they have a development partner without naming them, which is normal and rarely questioned. Some say nothing. Either way we will not confirm or deny involvement if approached directly, and we will tell you it happened.
If the overrun is ours, we absorb it, and that is written into the agreement. If it is caused by scope change or by information arriving late, we re-estimate before continuing rather than silently extending. The fortnightly staging build exists so an overrun is visible in week two rather than week ten.
Yes, as a member of your team, introduced under your name and using an address at your domain. Several partners use this for technical discovery, where a direct conversation saves a week of relayed questions. It is never our default and never happens without you arranging it.
Not formally, though anything under two weeks rarely justifies the setup on either side. Most white-label work runs from six weeks to several months. Maintenance retainers are the exception and can be small, because the context is already loaded from a previous build.
You keep everything built to that point, in your repository, with the documentation written to date. We hand over in a scheduled session rather than an email, and we do not hold code, credentials or environments as leverage. There is no exit fee.
What clients say on Google
Unedited, pulled live from our Google Business listing.
Loading reviews from Google - read them on Google.
Need delivery capacity this quarter?
Send an outline of the work and we will scope it in writing, ready for you to price.
- USD
- EUR
- GBP
- CHF
- SGD
- AUD
- CAD
- AED
- SAR
- QAR
- JPY
- INR
Card, netbanking, wallet and UPI through Razorpay, which is what our checkout runs on, so anything it accepts we accept. Bank transfer, SEPA, Wise and Payoneer for invoices that prefer it.
NDA before the first call. Full IP assignment on delivery. Contracts under Indian, English or Delaware law.