Platform Engineering

Rapid-application platform for government departments

A citizen bill-payment MVP shipped in 45 days that doubled as the first tenant of a multi-tenant rapid-application platform — six primitives (identity, lookup, payment, workflow, audit, tenant) composable into any government department's citizen-facing app.

2026Client: Confidential · Government sector (NDA)LaravelPHP 8.3Multi-tenantReact Native1LINK 1BILLWorkflow EngineGitHub Actions

Skills & Technologies

Rapid Application FrameworkMulti-tenant PlatformsStateful Workflow Engines

The shape of the engagement

45 days

Kickoff to MVP live

13

CodeFellow team at peak

6

Platform primitives

0

Rebuilds per new department

We were hired to ship a citizen bill-payment MVP. Three weeks in, the partner's CTO asked how long a second department's portal would take — and the honest answer rewrote the engagement. The MVP became the first tenant of a rapid-application platform built on six primitives: identity, lookup, payment, workflow, audit, and tenant. Each is a Laravel package; a department app is a declarative composition of those, plus whatever raw Laravel the department actually needs.

We shipped the MVP in 45 days flat without letting the platform delay the launch. The platform deliberately avoids being a low-code prison: configuration is PHP, every primitive is Laravel underneath, multi-tenancy is a day-one primitive, and there are escape hatches everywhere. It's leverage, not a jail.

Read the fullcase study

The long-form write-up covers the mid-engagement pivot, the six primitives, the architecture that kept us out of the low-code trap, and the five lessons of an MVP-to-platform build.

NDAs welcome. First call is on us.

Back to Projects