From owned PHP tool to defensible multi-tenant SaaS - before customer one
B2B SaaS - awards and programme management platform for EU conference organizers, rebuilt from scratch with a production-grade architecture.
An existing PHP awards tool with no path to multi-tenant SaaS. The target market - EU conference organizers running recurring awards programmes - was underserved by incumbent platforms on data residency compliance, conference-tool integrations, and pricing transparency.
The product needed to be rebuilt from scratch with a defensible architecture before approaching the first paying customer. There was no technical co-founder, no prior SaaS codebase, and no margin for a foundation that would need to be replaced at scale.
-
→
A three-level programme hierarchy built on generic domain primitives - supporting awards, CFP, and scholarship types from day one, without future schema changes. Multi-tenancy enforced at the data layer, not in application code, so every isolation guarantee is structural rather than accidental.
-
→
An architecture specified against concrete legal and operational constraints - EU data residency, billing tax compliance, and async job reliability each drove a component decision. No defaults, no preferences - every choice has a documented rationale the founder can defend to an investor or auditor.
-
→
An AI-agent-ready implementation brief - a structured document covering schema design, access control patterns, role model, API conventions, and environment setup. It replaces both a traditional technical specification and the need for a technical co-founder: the founder can hand it to any capable coding agent and begin building immediately.
-
→
A formal deferred features registry with versioned go/no-go gates - white-label, AI-assisted review, and multi-language UI were each documented with the conditions under which they become viable. Scope creep is the most common reason early-stage products miss MVP dates; this registry makes the boundary explicit and reviewable.
-
→
Fifteen pre-production artifacts delivered before the first line of product code - four GDPR-compliant legal documents with parametric placeholders, seven launch checklists, eleven transactional email templates, and interactive flow diagrams. The founder arrived at implementation with the compliance and operational groundwork already done.
Realistic MVP timeline - replacing a 12-week plan that would have collapsed under multi-tenancy edge cases and billing complexity.
Schema migrations needed for expansion - CFP and scholarship types supported by the initial data model without structural changes.
Compliance groundwork compressed - four GDPR-ready legal documents delivered via parametric templates in a single engagement.
Founder needed to direct the build - the implementation brief enables full MVP delivery without an architect or technical co-founder.
The founder ended the engagement with everything needed to begin building - and nothing that would need to be rebuilt when the first customer arrived.
- The 17-week timeline came with a reason for every week added. Each scope item was justified against a specific failure mode in the original 12-week plan - making the timeline defensible, not just conservative.
- Compliance documentation was ready before the first line of product code. Four GDPR-compliant legal documents - covering data processing agreements, right to erasure, and cookie policy - delivered with parametric placeholders for the EU market from day one.
- The implementation brief gave the founder full directorial control over the build - with or without a technical co-founder, using any capable AI coding agent to execute against a specification the founder can understand and own.
I had a PHP tool, a clear market gap, and no technical co-founder. Darkbloom gave me a complete architecture, a realistic plan, and a brief I could hand to a coding agent and actually trust. I stopped worrying about whether the foundation would hold.- J.V. · Founder · Awards Platform (private)