Selected projects and product work

What was built, and where a person still decides.

Client names and figures are withheld. Each note states the problem, what the system does now, where a person decides, and whether we built it, scoped and reviewed it, or it is a product of a separate company our founder co-founded. The pictures are schematics, not screenshots.

Booking, member and customer systems

A timetable, a member list, and the money around them.

What we check before building one of these is set out on the booking and member systems page.

Health clinic · Online booking

Online booking with deposits, and follow-ups that survived a platform change

Built by usIn use

Before: The clinic's booking tool could not pass booking details to other systems, so intake forms and review invitations could not be triggered automatically.
Now: We built booking with deposits and practitioner rosters into the clinic's website, then moved bookings to a product its staff preferred while keeping the connection for follow-ups.
Who decides: Staff mark each appointment attended or missed and collect the remaining payment.

Schematic, not a screenshot

Wellness retreat · Membership

Tiers, prepaid balances and vouchers on one member record

Built by usIn use

Before: Memberships and vouchers were sold at the counter and online, with no single record of who was a member or what they had prepaid.
Now: One member record holds tiers, balances, vouchers and marketing consent. The system reads upcoming bookings and sends the matching form before each visit.
Who decides: The owner approves every campaign before it goes out.

Schematic, not a screenshot

Private tuition · Scheduling

Lesson slots, prepaid packs and balances on one calendar

Built by usIn use

Before: Lesson bookings, payments and prepaid balances were tracked separately, so it was hard to see who owed money or who was about to run out of credit.
Now: Lessons are booked into empty calendar slots and repeat weekly. The system tracks credits bought and lessons used for each prepaid pack.
Who decides: The teacher confirms each bank transfer and decides when a late cancellation is charged.

Schematic, not a screenshot

Care workforce · Shift platform

Shifts published by providers, claimed by workers on their phones

Product scoping and reviewIn use

Before: Care providers filled vacant shifts by phone and checked compliance documents by hand.
Now: Providers post shifts on a calendar, including recurring ones. Workers accept or decline from a mobile web app, mark when they are unavailable, check in on site and submit timesheets. We defined the requirements and reviewed delivery; the client's own development team built the platform.
Who decides: Providers shortlist and hire, and timesheets pass through named approvers.

Schematic, not a screenshot

Connecting systems and reporting

Systems that already exist, made to agree.

Specialty retail · Several stores

Sales, stock and payroll records made to agree

Built by usIn use

Before: Sales, stock and payroll records were held in separate tools, and order history was slow to retrieve.
Now: A central database combines in-store and online orders, produces the weekly sales, reorder, picking and labour reports, and flags roster discrepancies for payroll review.
Who decides: Procurement decides what to buy. Payroll staff review every flag before pay is keyed in.

Schematic, not a screenshot

Training and education · Enrolment

Enrolment, attendance and pay from one record

Built by usIn use

Before: Enrolment, class rolls and staff timesheets had grown into separate spreadsheets that had stopped agreeing with each other.
Now: Recurring courses generate their class slots automatically. The enrolment, the roll and the hours a teacher is paid for are drawn from the same record.
Who decides: Teachers record attendance and hours; office staff check the record before payroll.

Schematic, not a screenshot

Real estate · Listings website

Listings synced from the agency's client management system every night

Built by usIn use

Before: The agency's website was hosted inside its client management system and had fallen behind.
Now: The site pulls listings from that system overnight, saves enquiries, and redirects old article links to their new pages.
Who decides: Agents decide what is featured by ticking it in their existing system. Buyer and rental alerts were deliberately left there.

Schematic, not a screenshot

Financial advisory · Automated assistant

A morning brief when a follow-up is due, and no client email sent without a yes

Built by usIn use

Before: Client records, email and follow-up tasks were held separately, and follow-ups depended on memory.
Now: A private, automated assistant reads the adviser's mailbox and calendar and sends a morning brief when a follow-up is due or a deadline is approaching. When nothing has changed, it says nothing.
Who decides: No email to a client leaves without the adviser's explicit confirmation, and anything written to a client record can be undone.

Schematic, not a screenshot

Document processing and review

Work prepared by the system, judged by a person.

Accounting practice · Business activity statement review

Every flagged item links to the transaction behind it

Built by usIn staff testing

Before: Activity statements were reviewed by hand against a checklist, with reports exported from the ledger one at a time.
Now: Staff are testing a system that prepares review findings from ledger data with read-only access. Each finding links to its source transaction and is written into the checklist the firm already uses. It runs in the firm's own cloud environment, and the firm has not yet formally accepted it.
Who decides: Staff mark each finding as agree, disagree or need more information. Judgement and lodgement stay with the firm; the system cannot change the books.

Schematic, not a screenshot

Recruitment · Document checks

Candidate documents checked before a person reviews the file

Built by usIn use

Before: Roles with eligibility and certification requirements meant every candidate arrived with paperwork, and most of the effort went into chasing it.
Now: The system reads applications against the role's criteria, asks candidates for what is missing, and checks the documents that come back.
Who decides: Anything it cannot confirm goes to a person. It prepares the file; it does not decide who is hired.

Schematic, not a screenshot

Resources sector · Document search

Answers linked to the source document

Built by usIn use

Before: Years of contracts, procedures and compliance records had accumulated, and staff struggled to find the document they needed.
Now: Staff ask a question in plain language and get an answer with the source document attached.
Who decides: Staff check each answer against the attached source before relying on it.

Schematic, not a screenshot

Records for regulated work

A record produced as the work is done.

On every compliance build the division of labour is the same. Your advisers define the process and the retention requirements. We build the agreed workflow and record its configured steps and approvals. We do not certify that the process itself meets your obligations.

Real estate · Anti-money-laundering records

A case file with an append-only activity log

Built by usIn use

Before: New anti-money-laundering obligations arrived at an agency whose client files were spread across a shared drive.
Now: Each client has a staged case file, from client type and identity checks through to sign-off, with an activity log that can only be added to and one PDF per case for the reviewer.
Who decides: Staff assess every possible sanctions match and set the risk rating, and a reviewer signs off. The tool makes no compliance judgement of its own.

Schematic, not a screenshot

Fleet operations · Compliance records and app

Compliance records flagged before they expire, with the fleet in an app

Co-founded productIn use

Before: Registrations, inspections and driver licences were tracked in spreadsheets, so somebody had to remember to look.
Now: Vehicle records, inspection evidence, expiry dates and live location sit together. Fleet managers use an iOS and Android app built from one codebase on the same records as the web system. It is a product of a separate company our founder co-founded, not a Praxis Arc client delivery.
Who decides: An inspector submits the record and a manager approves it. The system sends reminders and keeps the record; it does not decide whether a vehicle passes inspection.

Schematic, not a screenshot

Happy to talk any of these through in detail, including what we would do differently. Request an initial call.