The stack
That one Excel file, turned into real software.
No permissions, no validation, no backup, and one person who understands it. Every Swedish SME has one, and it is usually the most load-bearing thing in the company.
What is specified, not assumed
- Integrations
- accounting · payments · id
- Validation
- server-side, enforced
- Audit trail
- who changed what, when
- Backup
- daily · restore tested
FIG. 1 — Business systems
What we ship in this layer
Booking & scheduling
Availability, reminders and cancellations handled properly, including the awkward cases — double bookings, no-shows, timezone drift.
Quoting & invoicing
From enquiry to paid invoice without anything being retyped between two systems that were never introduced to each other.
Registers & inventory
Members, stock and assets tracked in one place, with a history you can audit rather than a spreadsheet nobody dares delete.
Backends & APIs
REST or GraphQL, documented, versioned and testable — built so the next developer can read it without ringing you first.
Integrations
Accounting, CRM, payments and email talking to each other reliably, including what happens when one of them is down.
"That one Excel file"
The spreadsheet holding your company together, turned into software with real permissions, real validation and a real backup.
The seams between systems
Most of what breaks in a small company breaks between two systems, because no single supplier owns both sides. Accounting, payments and identity included — and a defined behaviour for when one of them is down.
Failure modes are specified, not assumed.
Say what is broken. Or what is missing.
One number and one date come back in writing, from the person who will do the work. Nothing starts, and nothing is owed, until you approve.