Biodiversity Net Gain Software Without Boiling the Ocean

Biodiversity Net Gain (BNG) turned a planning obligation into software demand. The trap is building a "compliance platform" that tries to be legislation, CAD, CRM, and finance in one MVP — then shipping nothing that a homeowner, consultant, or developer can actually use.

This guide is for founders and product owners building biodiversity net gain software or adjacent UK land/compliance products. It is not legal advice and not a claim of certification authority. Soft proof comes from YourSTS, where we helped take a compliance-shaped platform from idea to an MVP that supports real operational use.

What BNG software must prove

Strip the acronyms. A useful product proves a small set of operational truths:

Who the actor is
Homeowner, developer, consultant, or authority-facing role — each needs a different job-to-be-done. One login that pretends everyone is the same user will lie to someone.

What site or project is in scope
Identity of the land/project, status, and the artifacts tied to it. Orphan documents in email are not a system of record.

What evidence exists
Surveys, plans, metrics, agreements — whatever your v1 claims to track must be attachable, versioned enough to trust, and findable later.

What happens next
A clear workflow: submitted, in review, blocked, complete. If the product cannot show the next action, users return to spreadsheets.

What "done" means for your buyer
For an MVP, "done" might be "projects can be created, evidence attached, and status shared with the parties who need it" — not "we automated Natural England."

If you cannot write those five lines for your buyer, you are not ready to price a build.

MVP boundary vs full compliance platform

Boiling the ocean looks like: encoding the entire BNG policy surface before five users complete one path. Compliant enough for v1 looks like: the path your first segment must run weekly, with evidence and status they trust, plus an explicit list of what a human still does offline.

YourSTS-shaped lesson: define MVP scope early so you do not spend the runway on elegance nobody can operate.

Data and workflow traps

Legal cosplay
Software that "is" the regulation invites liability theatre. Stay in operational tooling: capture, track, notify, report. Send users to qualified advisors for legal interpretation.

Evidence without ownership
Files in a bucket with no project, role, or status become a second email inbox.

Status without SLAs
"In progress" forever is how trust dies. Even a simple due date beats ambient green badges.

Multi-party confusion
If homeowners and consultants share a queue with no role boundaries, support volume will teach you roles the hard way.

Integration fantasy
Bank-grade or authority-grade APIs may not exist for your wedge. Scope the human bridge; do not invent a partner API on the roadmap slide.

Soft proof: YourSTS

YourSTS needed a platform built from scratch with enough clarity to avoid wasted effort. We helped shape direction, define MVP scope, and build a foundation for real operational use. Public outcome shape: MVP in about two months, later supporting hundreds of homeowners and hundreds of development projects across the UK, with a Natural England–aligned compliance path called out in the case study — not as a certification claim, as a product direction.

Scope before you buy a pitch deck

Fill the integration scoping template with your actors, evidence types, definition of done, and what stays manual in v1. Send the same brief to every vendor.

If you already have a concrete module and integration plan, use the architecture review for written feedback within 48 hours.