Skip to content
AspirecoStart

Capabilities / I

Custom software

The systems that run the business. Ledgers, portals, back offices, admin tools — built when the off-the-shelf thing stopped fitting three compromises ago.

In shortAspireco builds the software that runs a business: operational platforms for quoting, job costing, inventory and scheduling, with real double-entry books underneath. It is for operators whose work has outgrown off-the-shelf tools and now lives in spreadsheets and systems that disagree.

What we deliver

  • Operational platforms — quoting, job costing, inventory, scheduling
  • Real double-entry accounting: every document posts a balanced journal entry
  • Role-based access modelled in the schema, not bolted on in the view layer
  • Money as integers, quantities at six decimals — no float drift in your books
  • Migration paths off spreadsheets, Access databases and abandoned SaaS

A 45-table contractor platform where leads, estimates, jobs, bills, timesheets and change orders all resolve into one balanced general ledger — and a demo dataset that renders byte-identical whether it runs on the embedded WebAssembly Postgres used locally or the managed Postgres in production.

Where we do this

Aspireco works remotely across Canada. These are the places close enough that being in the room during discovery is practical.

Platforms we build it on

Industries we have built it for

Questions about custom software

Have you built an operations platform like this before?

Yes. Contractor OS is our own: a 45-table platform where leads, estimates, jobs, bills, timesheets and change orders all resolve into one balanced general ledger. Its demo dataset produces byte-identical figures on the embedded WebAssembly Postgres used locally and the managed Postgres in production, with the balance sheet out by exactly 0.00 on both. Oryx, a distribution platform we are building now, applies the same approach: one application for a storefront, dealer portal, back office and sales CRM over a single ledger and permission model.

Why does an operations platform need a real general ledger?

So the operation and the books cannot disagree. In real double-entry accounting every financial document posts a balanced journal entry, so job costs and margins come from the same records the crew works in rather than from a second system. Money is held as integers and quantities at six decimals, so nothing drifts a cent at a time through floating-point rounding. The payoff is a March with no surprises.

Can custom software control what each role can see and do?

Yes, and that belongs in the schema rather than bolted onto the screens. Contractor OS defines seven organisation roles — owner, admin, project manager, estimator, accountant, field and viewer — as a first-class enum rather than a string on the user record. Oryx goes further and scopes permissions to the row: a rep reading crm:read:own gets a query confined to their own records, enforced below the interface.

Can you move our business off spreadsheets or an Access database?

Yes. Migration paths off spreadsheets, Access databases and abandoned SaaS are a standard deliverable. The free audit first maps what your current setup actually does and what is safe to keep. A build then carries a migration, cutover and rollback plan, so the old workbook stops being the system on a planned day rather than whenever someone forgets to update it.

What drives the cost of a custom software build?

Scope: how much of the operation moves into one system, how many outside systems it has to talk to, how many roles the access model carries, and how much existing data has to migrate. None of that can be priced honestly before someone has looked, so it is scoped and priced in writing after the free audit. The build that follows is fixed scope at a fixed price, delivered in weekly increments against a working slice.