Skip to content
ServicesOur WorkAbout
Let's Talk
NavigateMENU / 04
01About
02Our Work
03Services
StrategyCreativeWebsite DevelopmentSoftware DevelopmentBusiness Automation
04Contact
More
BlogFlight Program
Elsewhere
Business Operating Systems

Bespoke software your business owns, built to make everything above it cheap.

The moat is your data. You're renting it back one seat at a time.

We counted ours: eleven SaaS tools, low tens of thousands a year, and one definition of a client that none of them agreed on. We replaced the lot with software we own, and it runs on about forty dollars a month. We've since built the same thing for a creator agency and an events company, and the pattern holds.

Premise

“The consolidation matters more than the ownership.”

From our own write-up of the build

When your systems are disjointed, velocity in your organisation comes to a standstill. It creeps along, because every platform holds its own copy of companies, contacts, IDs, revenue, hours and budgets. Those copies drift. They get quietly, increasingly wrong, and the work of reconciling them never appears on anyone's job description.

That used to be a tax on your people. Now it also decides what you're able to build on top. An agent can't reason across four systems that disagree about what a client is. Silos don't just slow humans down anymore, they blind whatever you put above them.

Three costs

One you can see, two you can't.

01

The bill you're paying

The visible one, and the least interesting of the three.

Per-seat pricing means growing your team costs you money before it makes you any. Per-contact pricing means succeeding at marketing costs you money. And the features you actually need are usually one tier above the one you're on.

These are our old line items, at list price. Yours will look different in the details and identical in the shape.

02

The bill nobody sends you

Larger than the first one, and invisible on every P&L.

Twenty minutes of actual work, then nine days of everything else. Someone rekeying a client record into a third system. A project manager reconciling hours against a budget that lives somewhere the timesheets can't see. Reports assembled by hand every month because no single tool holds enough to produce them.

There's a revenue side to this too. We lost tens of thousands of dollars a year, easily, in work we were qualified to do and clients wanted to buy, that we either gave away or never got to. Not because we couldn't do it. Because nothing in our stack surfaced it in time.

03

The position you're taking

The one that decides what the next five years cost you.

Model economics are moving quickly, and they'll keep moving. The frontier labs are worth their price for hard reasoning today. Cheaper models are arriving with genuine expertise at a fraction of the cost, and for a large share of the work they're already sufficient.

Getting that benefit requires being able to swap what's underneath at short notice. If your intelligence is delivered inside somebody else's product, you can't. You take the model they ship, at the price they set, on the timeline they choose. Owning the layer underneath is what turns that from a lock-in into a purchasing decision.

What it replaced

Our stack before, at list price.

Eleven tools, each solving part of the problem, none of them agreeing on the shape of a client. Our real spend ran into the low tens of thousands a year. Airtable alone was five to six thousand.

Paper Crane's previous SaaS stack with list prices
ToolList priceWhat replaced it
HubSpot Sales Hub Professional~$90 / seat / moCompanies, contacts, deals, leads
HubSpot Marketing Hub Professionalfrom ~$800 / moCampaigns and sequences
Copper$59 / seat / moCRM, at a different time
Airtable$20 to $45 / user / moRecords and relationships
Monday.comthousands, on the tierProjects, phases, sprints, tasks
Harvest$9 to $14 / seat / moTime tracking
Zapier, Make, n8n~$2,000 / yrGlue between all of the above
Dext, Formspark, FilloutassortedReceipts and forms

What replaced it runs on about forty dollars a month: 173 pages and 120 API routes, 185 database tables over 110 migrations, 44 background functions and 24 scheduled automations. Xero stayed, integrated rather than replaced, because accounting is not a thing you should build.

The build is not in that number. That's the honest part, and it's covered further down.

Architecture

Own the top three rows and you can change the bottom one whenever you like.

This is the whole mechanism. Your data lives in your database. Your logic sits on top of it. Models are reached through one interface rather than wired individually into forty features. Swapping providers changes the bottom row and leaves everything above it alone.

How model portability works: three owned layers above one swappable oneYour data sits in your own database. Your application sits on top of it. Every feature reaches models through a single interface. Providers sit below that interface, detached, so changing provider leaves the three layers above untouched.YOUR DATAone database, one definition of a clientYOUR APPLICATIONthe logic your business actually runs onMODEL INTERFACEone place every feature calls throughYOURS, ABOVE THIS LINERENTED, BELOW ITClaudeGPTOpen modelsWhatever's next

Your data, in one place

One definition of a client, a project, an hour and a dollar. Every layer above this depends on it, which is why we say the consolidation matters more than the ownership.

One interface, many providers

Features call an interface, not a vendor SDK. Changing model means changing configuration rather than rewriting the features that depend on it.

What portability doesn't cover

Prompts and evals are tuned per model, and swapping means re-running them. Portability makes the switch a week of work instead of a rebuild. Anyone selling you costless switching is selling you something.

Built and running

In production, and owned by the people who run them.

MODERNSPEAK

A creator-management agency. We modelled the whole operation in Airtable first and ran the business on it, which proved every process and then showed us its ceiling. Then we rebuilt it bespoke on Supabase and Next.js: batch invoicing with province-aware tax, commission split on issue, a passwordless creator portal, and AI desk tools grounded in the agency's own roster data.

Read it →
per-seat fees, at any headcount
0

per-seat fees, at any headcount

AI tools, each grounded in their own data
18

AI tools, each grounded in their own data

Xero sync keeping books and commission in step
2-way

Xero sync keeping books and commission in step

SocialNext

Conferences, summits and speaker series across Canada. Years in Notion, then Airtable, then rebuilt as an application they own. The schedule builder alone gave them back most of a working week on every event they run.

Read it →
of admin saved per event, on one feature
~16 hrs

of admin saved per event, on one feature

of records migrated with history intact
100,000s

of records migrated with history intact

cut from tooling each year, five figures ahead
$1,000s

cut from tooling each year, five figures ahead

Two ways in

Prove it cheaply, or go straight at it.

Which one is right depends on how well you already know your own processes. We'll tell you honestly which door you're standing in front of, and it's frequently not the one people expect.

A

Model it first

For teams whose processes live in people's heads

  1. 01We model your whole operation in something cheap and fast, usually Airtable or Notion.
  2. 02You run the business on it for a real stretch. Months, not a demo.
  3. 03It proves what works, and it finds the ceiling, which is the actual deliverable.
  4. 04Then we rebuild it bespoke, carrying the proven workflows across intact.

This is the path MODERNSPEAK took. The MVP validated every process and ran a real business before a line of bespoke code existed. When per-seat costs and interface limits started fighting them, we already knew exactly what to build.

B

Straight to bespoke

For teams already paying rent on processes they know cold

  1. 01Discovery against the systems you already run.
  2. 02We build on the Paper Crane OS, so auth, permissions, real-time, exports and integrations are there on day one.
  3. 03We migrate your records with their history, rather than starting you at zero.
  4. 04We stay on as your technical partner.

If you already know your processes and your frustration is entirely about ceilings and per-seat pricing, the modelling step is a delay rather than a de-risk. SocialNext had years of operational history behind them when we rebuilt.

How it's scoped

Built in cycles.

We work in fixed cycles on our own substrate, each one ending with something you can use. How many an operating system takes depends on how much of the business moves and how much history comes with it, which is what the first conversation is for.

Cycles

not open-ended time

Each cycle has a shaped scope and a fixed length. You see working software at the end of every one, rather than a status update explaining why you haven't.

Yours

outright, at the end

The code, the data and the infrastructure. No per-seat fees, no vendor holding your records hostage, and no line item that grows every time you hire.

Optional

partnership afterwards

Some clients drop to dependency updates, others add flows every cycle. Thirty-day cancellation, and we wind down quickly when asked.

What it comes to depends entirely on how much of your operation moves. Bring us the stack you're paying for now and we'll scope it against that.

What we won't build you

Some of this you should never build.

Owning your software is the extreme version of consolidating your data, and it isn't the version most companies need. Here's where we say no.

  • Accounting and compliance. Xero stayed in our stack for a reason, and it should stay in yours.
  • Payments, messaging at scale, and deliverability. All genuinely hard, all solved better by people who do only that.
  • Anything where a bug means a customer's data or a regulator's attention. Internal tools fail politely. These don't.
  • Anything you don't understand operationally. Prompting your way to a CRM gets you a demo. It doesn't get you something a business can run on, because you won't know what to ask for.
  • A rebuild, when your actual problem is scattered data. Fix that first. It's cheaper, it's faster, and it's most of the benefit.
Related reading

The rest of the picture.

AI Integration: the field guide

Five layers of what AI integration actually means, from data plumbing up to agents that take action. An operating system is the foundation those layers assume.

How we build

Human-driven and AI-driven development, with the trade-offs laid out plainly. Worth reading before you decide how a build like this should be run.

AI Consulting

Your systems can be perfect and still go unused. If the gap on your team is fluency rather than infrastructure, start there instead.

We replaced 11 SaaS tools with software we built

The full write-up: every tool, every price, the bugs, and the parts we'd tell you not to attempt.

Start here

Bring us your stack and your frustrations.

Twenty minutes. Tell us what you're paying for, where your data actually lives, and which report takes someone a full day every month. We'll tell you whether this is a rebuild, a consolidation project, or something you should leave exactly as it is.

Book a call →
Paper Crane / Studio
CALGARYVANCOUVER·© 2026

A digital transformation studio building considered, durable web work for ambitious operators.

Services
  • Creative
  • Strategy
  • Website Development
  • Software Development
  • Business Automation
  • ─AI Automation
  • ─Workflow Automation
Navigate
  1. 01About Us
  2. 02Our Work
  3. 03Contact Us
Elsewhere
© 2026   PAPER CRANE MEDIA LTD.
Terms & Conditions
Privacy Policy