I started Septim Labs after watching a client pull up their monthly SaaS invoices on a shared screen. Fourteen line items. Three of the tools did overlapping things. None of the data lived anywhere they controlled. The total was more than they'd paid their last contractor to build the thing those tools were supposed to replace — and that contractor had handed over the repository and walked away. The SaaS vendors had not.
That was the argument. The studio opened in September of 2026 with one rule and one promise. The rule: every deliverable is an owned codebase. The promise: we charge for it once. Neither has changed.
You should own what you depend on. Pay once. Ship once. You keep it.
The name is deliberate. Septim — from Latin septimus, seventh — maps to September, the month the studio opened and the month I consider the studio's true season. September is when things that were planted in spring finally become useful. It is also, numerically, seven: the number of products in the original Forge catalogue, all pay-once, all yours on purchase. The number isn't decorative. It was a commitment: seven things I would finish and hand over before adding an eighth.
The work is not glamorous. I have shipped a work-order system for an auto restoration shop whose foreman was living inside three browser tabs and a spiral notebook. I have built an audit framework that turns a SaaS stack into a line-item receipt — so the person paying it can finally see what they are renting versus what they are using. I have, more than once, told a prospective client that what they described didn't need custom software; it needed a better spreadsheet and a free afternoon. Those calls are also the work.
The studio is a small team — fewer than ten people. That is not a disclaimer. It is the design. A small team finishes things. It does not accumulate half-built features, does not hand off context between departments, does not lose the thread of what a client actually asked for six weeks ago. The person who specced your project is the person who ships it.
What every engagement has in common: at the end, I hand over the repository, the deploy runbook, and a plain-language maintenance guide. The code runs on your infrastructure, in accounts you control, under credentials only you hold. There is no call-home, no usage telemetry, no feature flag that goes dark if you stop paying. Paying once means you paid. It doesn't expire.