White-label software development
Your customer buys from you, is invoiced by you and is supported by you. Behind that, our engineers write the code, review each other’s work, run the tests and ship the releases, in your repositories and under your name. One contract with a registered Ukrainian company, the intellectual property assigned onward to you, and a partner-side lead you can call.
When this is the right model
White-label suits a partner who already owns the hard part: the customer, the brand and the commercial relationship. You have sold work you cannot staff, or a customer wants a stack your own team does not carry, or you want to offer software engineering at all without building a department for it. What you need is engineering capacity that does not show up in your customer’s inbox with somebody else’s logo on it.
It is a model we already run. One of our current engagements is white-label delivery for a European partner, where our engineers work inside the partner’s tooling on a product sold under the partner’s name. We do not publish partner names, which is the same discretion you would get.
How we stay invisible
Being white-label is a set of specific arrangements, not a promise. These are the ones we make.
Your domain and your accounts
Our engineers work from mailboxes, chat accounts and repository identities you issue. Nothing your customer sees carries a bigtree108.com address unless you want it to.
Your repositories and your pipeline
Code lives where you keep it, reviewed in your process and released through your CI. We do not mirror it, and we do not need a copy of it after the engagement ends.
Your documents
Architecture notes, risk reviews, estimates and release notes are written so you can forward them unchanged. No logos to strip, no tone that does not sound like you.
Confidentiality written down, not assumed
The arrangement and what may be said about it are in the contract and in the briefing our people get on day one, rather than left to individual judgement on a customer call.
Due diligence we answer, not you
When your customer’s procurement asks about subcontractors, insurance, data handling or where the people sit, we supply the answers and the paperwork for you to pass on.
A clean exit
Notice runs both ways and is in the contract. On exit you get documentation, credentials and any environment we hold, without a commercial negotiation attached.
How an engagement runs
You send the brief, under NDA
The scope, a repository link or the problem list from a system your customer already runs. We sign your NDA first; you do not have to use ours.
We answer as you would
Within one business day you get the open questions, the approach and an estimate you can hold us to, written so it can go to your customer with your name on it.
A first deliverable you can judge
Small, shippable and with tests, before anyone commits a customer to a long engagement. If we are wrong for the work, this is where it costs least to find out.
Then it runs like your own team
Your process, your priorities, your releases, with our lead reporting to you on capacity, risks and what shipped. You keep the customer relationship throughout.
The ownership chain, in order
The question a customer’s lawyer asks is whether the person who typed the code can still claim it. Every specialist at BigTree108 signs a contract assigning all work product to the company before they are given access to anything. Our agreement with you assigns it onward to you, and your agreement assigns it to your customer. There is no gap in the chain and no point at which an individual developer retains rights to something you are selling.
Confidentiality runs the same way: an NDA with each specialist, an NDA with you, and a non-solicitation clause covering your customers that we sign without negotiation.
Pricing you can build a margin on
White-label work is billed per person, hourly or monthly, so you can put your own margin on top and quote your customer a number that works for you. We quote per engagement rather than publishing a rate card, because the stack, the seniority and the length of the engagement change the number. Everyone logs time in our own portal, you see the hours throughout the month, and the same figures produce the single invoice from BIG TREE 108 LLC at the end of it, so what you bill your customer and what you pay us reconcile against one record.
Including systems somebody else wrote
A large share of white-label work is not a new build but a system your customer inherited and you have now inherited too. We have taken over nine of them, the oldest written in 2008. A take-over starts with a read-only review and a written list of risks ordered by production impact, before anybody changes a line, and that review is written so you can pass it to your customer as your own document. Keeping such a system running afterwards is covered by managed application support.
If the need is capacity across several skills rather than delivery under your brand, the nearshore delivery pod is the closer fit, and the two are often combined.
Questions about white-label delivery
What does white-label software development mean in practice?
Your customer buys from you, is invoiced by you and is supported by you. Behind that, our engineers write the code, review each other’s pull requests, run the tests and ship the releases, using your repositories, your tracker, your CI and, where you want it, your email domain. Commit history, release notes and documentation carry your name. BigTree108 appears in your contract with us and nowhere else.
Will our customer ever find out the work is subcontracted?
Not from us. Our people are told at the start of the engagement what the arrangement is and what they may and may not say, and it is written into the contract rather than left to judgement. If your own agreement with your customer requires you to disclose a subcontractor, we will be named as one and will supply whatever due-diligence paperwork they ask for.
Who owns the code we deliver under our brand?
You do, and the chain is complete before anyone gets access. Every specialist has a signed contract with BigTree108 assigning all work product to the company, and our agreement with you assigns it onward, so there is no point in the chain where a developer retains rights to something you are selling to a customer.
How do you price white-label work?
Per person, hourly or monthly, so you can put your own margin on top and quote your customer a number that works for you. We quote per engagement rather than publishing a rate card, because the stack, the seniority and the length of the engagement change the number. You see logged hours throughout the month and receive one invoice from BIG TREE 108 LLC at the end of it.
What happens if our customer’s project fails or the relationship ends?
Notice periods run both ways and are agreed in the contract, not improvised. On exit we hand over documentation, credentials and any environment we own, and we do not hold your customer’s code or infrastructure hostage while a commercial conversation is running.
Can you take over a system our previous supplier built?
Yes, and it is a large part of what we do: nine such systems so far, the oldest written in 2008. A take-over starts with a read-only review and a written list of risks in order of production impact, before anybody changes a line. Under a white-label arrangement that review is written so you can pass it to your customer as your own.
Which technologies can you cover under our brand?
C# and .NET on Azure is our deepest practice, with Python beside it for automation, integration and data work, and Angular, React, Vue and Next.js on the front end, plus mobile, QA and test automation, cloud and DevOps, and design. More usefully for a partner: we are used to picking up whatever a project already runs on instead of steering it towards what we happen to know, because your customers will not all be on the same stack.
Have work you cannot staff?
Send the scope or the repository under your NDA. You get the open questions, an approach and an estimate within one business day, written so it can go to your customer with your name on it.