All case studies

Intrinsicomms Digital Ltd

Sapling

Building a UK ecosystem platform end to end, from market thesis to production infrastructure.

Role
Founder, product owner, and builder
Period
2025 to present
Status
In QA, pre-launch
Disciplines
Product strategy, Full-stack build, Go-to-market, Infrastructure

In one paragraph

Sapling is a Node.js platform I own outright. I wrote the thesis, specified the product, built it, secured it, hosted it, and designed the commercial model. It is currently in QA ahead of a UK launch under the Intrinsicomms group.

The situation

Working across UK higher education, green energy and B2B technology, I kept meeting the same structural gap. The people who need to find each other in a sector, the suppliers, advisors, institutions and buyers, have no shared place to be discovered. Each side pays for intermediaries to solve a coordination problem. That is a platform problem, not a marketing problem, and platform problems are worth building for because their value compounds with every participant added.

What was actually wrong

  • The ecosystem was fragmented across directories, LinkedIn threads and private networks, so demand and supply never met in one indexed place.
  • Existing tools were built for a single stakeholder type and broke as soon as a second one arrived with different incentives.
  • Nobody was capturing structured data on who was looking for what, so no one could price the demand.
  • For a solo founder, the honest constraint was cost. The product had to reach production without a funded engineering team.

The calls I made

Decision 01

Build rather than assemble

The cheap route was a no-code stack. I rejected it because the whole value of the product is the data model that links stakeholder types, and no-code platforms charge rent on exactly that. A Node.js application on infrastructure I control means the schema, the APIs and the migration path stay mine.

Decision 02

Own the infrastructure, not just the interface

I run the hosting on Hostinger, the domains and DNS, the API integrations, the SSL and security configuration, and the GitHub repository and deployment workflow. Owning the stack removes the vendor tax and, more usefully, means I can answer any technical question a buyer, partner or investor asks without a call to a developer.

Decision 03

Instrument before you launch

Analytics, search console and a SQL lead capture layer went in before the product was public. Launching without measurement is how founders end up arguing about opinions. Traffic during the build phase is deliberately UK-weighted; development and QA traffic from Pakistan is filtered out of the reporting view so the signal reflects the target market only.

Decision 04

Sequence the launch behind the parent brand

Sapling launches under IC Growth Engine alongside Micro Green Energy rather than alone. One shared acquisition engine, three products, one credibility story. Launching each in isolation would have meant paying the audience-building cost three times.

How it was done

  1. 01. Thesis

    Mapped seven stakeholder groups and their actual incentives, not their stated ones. Identified which two sides had to be present on day one for the platform to have any value at all, and treated the rest as later cohorts.

  2. 02. Specification

    Wrote the requirements myself: data model, user journeys, acceptance criteria, and the twelve month roadmap. Six productised services were defined so the platform had revenue paths that did not depend on scale arriving first.

  3. 03. Build

    Node.js application, SQL data layer, third-party API integrations, authentication and security hardening. Version control and deployment through GitHub, hosted on infrastructure I administer directly.

  4. 04. Discovery layer

    Search architecture designed in from the start: crawlable routing, structured data, a real sitemap, and an information architecture built around how the target market actually searches. This is the mistake I had already diagnosed in someone else's React app, so it was never going to be repeated here.

  5. 05. Commercial model

    Pricing and monetisation defined across B2C and B2B tiers, with the SQL lead layer feeding a qualified pipeline of ecosystem stakeholders rather than an anonymous mailing list.

  6. 06. QA and launch readiness

    Currently in structured QA: functional testing, accessibility, performance and pre-launch content governance, ahead of the UK go-live.

Outcome

  • A production-ready Node.js platform, owned and operated end to end, with no external development spend.
  • A structured stakeholder lead pipeline captured in SQL from the pre-launch phase onward.
  • A UK-focused analytics baseline established before launch, with build-market traffic excluded so the reporting view reflects the real market.
  • A defined commercial model and twelve month roadmap ready for the launch under IC Growth Engine.

Pre-launch analytics are UK-filtered and available on request. Figures will be published here once the product is live and the numbers are stable enough to be worth quoting.

What I took from it

The most valuable thing about building it myself is not the saved budget. It is that I now argue about roadmap trade-offs with real information about what each one costs to build.