What we built, and what it took.

The problem

Security, resilience and defence professionals had no shared place to find suppliers, compare capability, or ask each other questions without doing it in public. The information existed, scattered across directories, PDFs and private networks, and finding any of it took hours.

The founder knew the sector precisely and had no technical background. He was explicit that he did not want a team that would simply build to a spec — he needed one that would make good decisions when he could not.

Our approach

We took ownership of the product decisions rather than asking him to make technical calls he had no basis for. That meant deciding what to build first, what to leave out, and pushing back when a request would have created work without creating value.

The platform was built in slices, each one usable on its own, so there was something real to react to within weeks rather than a single reveal at the end.

What we built

• Community forums Threaded discussion with moderation tooling, built for professionals who cannot use a public platform.
• Natural language search LLM-powered search across the supplier database and discussion history, so a question in plain English returns the right record.
• Supplier database More than 7,000 suppliers, structured and searchable, with the ingestion pipeline to keep it current.
• Platform foundations Authentication, roles, billing and infrastructure — built once, properly, so the product could grow without a rewrite.

The outcome

A live platform serving the sector, with the supplier database, natural-language search and community all in production. The founder owns the codebase and the infrastructure outright.