What running products taught us

What running them has taught us.

We’ve shipped to both stores.

App Store review, Google Play release, push notifications and offline sync, done for our own products.

We’ve handled money and rules.

Billing, tax treatments and payment deadlines, written as tested code. Your product gets the same.

We answer the support tickets.

We support these for their users every day, so we know what keeping a SaaS running takes.

In development

What we’re building next.

Our own roadmap, and the shared building blocks that make every client project start further ahead.

Assistants that do the job, not the demo

Software that drafts the document, reads the tender, prices the work and hands a person something to check. The hard part is everything around the model: what it may see, what it costs per call, and what happens when it’s wrong.

Products for trades nobody builds for

The same approach as Estimark, pointed at other working lives that run on paper, WhatsApp and a whiteboard because no product was ever written for them.

The parts every product needs twice

Billing, permissions, audit, offline sync and document generation, built once and reused. It’s why a second product costs a fraction of the first.