White-label platform or custom build?

Most articles on this are written by someone who only sells one of the answers. We do both.

software built as custom
FIG. 00 — software built as custom

Google this question, and every result is published by a company that sells one of the two answers. The white-label vendors have total cost charts ending in their favor. The custom shops have charts ending in theirs.

We do both. We’ve white-labeled and customized an established platform for a client who needed to be live for a program launch; we’ve built products from scratch for clients whose software is the product they sell, and we license our own products out for other organizations to run under their brand. That’s the only reason this article can give you a straight answer.

The 3-year shape

White-labelCustom
Year 0Setup, configuration, brandingDesign and build
Year 1–2Subscription, per-seat, per-transactionHosting and maintenance
Year 3+Subscription plus the success taxHosting and maintenance

The success tax is the part people miss. Most white-label pricing scales with the product you’re trying to grow: users, transactions, seats. Vendors in this space describe annual price increases of 15 to 30% as common in the current market, and one analysis puts SaaS total cost of ownership at 2.5 to 4 times the headline price once implementation, integration, and internal admin are counted.

On the other side, a white-label build can genuinely cut initial development cost by 60 to 75%, according to a vendor who sells white-label apps. For a lot of organizations, that’s decisive, and correctly so. Being live in 6 weeks with 70% of what you wanted beats being live in 9 months with all of it, when the program date is impending.

The 5 questions that decide it

  1. Is your workflow the median? White-label platforms are optimized for the middle of their market. If your differentiation is the process, that difference can’t be purchased off the shelf.
  2. Does their pricing model fight your business model? Per-seat pricing on a product you sell per-organization is a structural problem that gets worse as you succeed.
  3. Is the software the product, or the supporting act? A foundation running a member app is buying a tool. An accreditation body whose assessment platform is the service it sells is buying its own product from somebody else.
  4. How much configuration does it take to fit? When the configuration quote for a white-label platform approaches the cost of a build, then the platform wasn’t built for your use case.
  5. What does leaving look like? Ask for a data export, in writing, before you sign. A lot of pain can come from data you can’t take with you.

Which one wins

When the white label wins

You have a real date, and 6 weeks is the honest runway.

Volume is uncertain and you’re still testing whether there is actual market demand.

The compliance burden is heavy and the vendor carries it.

Your organization has no appetite to own software, now or later.

When custom solutions pay for themselves

The workflow is the differentiator.

Per-unit fees have started scaling with your growth.

You’re paying for a whole tier to get 1 feature.

Integration with your existing systems is the actual requirement.

The data accumulating inside the platform is the asset.

You intend to license or sell the product itself.

Got a white-label option and a build decision having a Mexican standoff across the table? Book a discovery session, and we’ll tell you which one we’d take in your position.

Studio137

Continue reading

The Signal Desk Briefing

Stay close to the signal.

A concise monthly briefing on technology, design and the business systems connecting them. Delivered straight to your inbox.

One useful briefing each month. No noise.