Most operating problems are one problem: nobody can say what state a job is in, who owns it, or what it earns. We make those explicit while the work is running, not after someone assembles a report.
A platform should make the operation legible, not bury it under configuration.
Work is described as with finance, nearly done, or waiting on the client. Those are descriptions, not states, and nothing can be counted, escalated, or automated until they are.
A job advances because someone remembered to follow up. When that person is away it stops, and the client notices before the business does.
Price, cost, VAT, and what is billable are settled in spreadsheets and heads, so operations and finance describe the same month differently.
The handful of records the business actually runs on, the states each one can hold, and which transitions between them are allowed.
Every record has one owner at every moment, and each role gets the actions, visibility, and safeguards its job needs, without the rest.
Pricing, cost, approval thresholds, billing, and VAT expressed in the platform, so the operational record and the financial one are the same record.
Bring the data that has to come, keep the specialist tools worth keeping, and settle which system owns each record before anything is switched off.
Pixelity built Wazzan Holding a short-term-rental cleaning operations platform: four roles, scheduling that respects conflicts, travel and leave, photo-evidenced completion, VAT invoicing, and bookings syncing from Guesty, Hostaway, and Lodgify.
We have built internal and group-level business systems for AMKM Investments.
Qualification, quoting, approval thresholds, and the handover into delivery, with the numbers landing in the same system that runs the work.
Write down the records the business runs on, the states they move through, who owns each one, and where the commercial rules currently live.
OutputOperating model and record map
Design role by role, decide what each system owns, and plan migration and rollout around the records people must trust on day one.
OutputBlueprint, migration, and rollout plan
Configure or engineer the platform in connected stages, with permissions, reconciliation, and reporting present from the first one.
OutputA platform running real work
Extend modules, controls, and reporting as adoption widens and the commercial model changes.
OutputGrowth without losing ownership
A role-based platform where every item carries a state, an owner, and a number, from daily activity through approvals and reporting.
Open the demonstrationDecide deliberately which system owns each record. Two authoritative copies is not redundancy, it is a future argument.
Keep standard rules and genuine exceptions apart. An exception written as a rule quietly becomes the rule.
Plan migration, permissions, reconciliation, and reporting before the old tool is switched off, not after.
Describe it in a sentence or two. We will come back with what we would build first, what it would take, and whether you actually need us for it.