Skip to content

Praxis Arc Pty Ltd  ·  Perth, Western Australia

Systems that hold up.

Business systems and practical AI for small and mid-sized Australian firms, built and maintained from Perth. Where an output affects a decision, a person reviews it first.

The initial call is free. Paid scoping starts only after you approve what it covers and what it costs.

At a glance

Experience behind the work

20+ Years' experience
10+ Sectors worked in

Systems we work with

Xero Xero Practice Manager Shopify Square Stripe Microsoft 365 Google Workspace Monday.com Wix Bookings

What we do

Four kinds of work.

Most engagements start the same way. Staff are copying information between tools, keeping separate spreadsheets, or relying on memory to follow up. We turn that into a system, usually on top of the tools the business already pays for. Often the right answer is a better-designed process or two systems properly connected, with no AI involved at all, and we say so.

Booking, member and customer systems

Bookings, member accounts, prepaid balances and online orders connect to the records your staff use. Where a mobile app is needed, it uses those same records. Built as your own system, under your own accounts wherever that is practical.

Booking and scheduling Membership and loyalty iOS and Android apps

What we check before building one  ·  Example: clinic booking

Connecting systems and reporting

We connect point of sale, online store, rostering and accounting, then build the reports that need all of them. We also build tools that answer questions about your business data and show the records behind each answer.

Sales, stock and accounting in one view Scheduled management reporting Questions about your business data

Example: a retailer with several stores

Document processing and review

We build tools for practices that process large volumes of regulated paperwork. We take what arrives, pull out the fields that matter, check them against the rules that apply, and put anything uncertain in front of a person with the source attached.

Business activity statement review Client onboarding packs Candidate document checks

Example: activity statement review

Records for regulated work

Some processes exist so that, years later, somebody can prove what happened and when. We build the agreed workflow so the record is produced as the work is done, with an activity log that can only be added to.

Your advisers define the process and the retention requirements. We do not certify that the process itself meets your obligations.

Anti-money-laundering records Inspection and compliance cycles

Example: anti-money-laundering case files

Selected projects and product work

Three examples.

Client names are withheld. The pictures are schematics, not screenshots.

All project notes
Schematic: a clinic day sheet with three practitioner columns, deposits paid and one no-show flagged. DAY SHEET PRACTITIONER 1 PRACTITIONER 2 PRACTITIONER 3 8:00 9:00 10:00 11:00 12:00 Booked Booked Booked Booked Booked Booked Booked Booked Booked Booked Booked No-show Deposit paid Deposit paid Deposit paid Deposit paid Deposit paid Deposit paid Deposit paid Deposit paid Deposit paid Deposit paid Self-reschedule Open Open Open

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: a stock table across stores and warehouse with one empty line feeding a reorder report. STOCK BY LOCATION PRODUCT A PRODUCT B PRODUCT C Store 1 Store 2 Store 3 Warehouse Empty Reorder report → procurement

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: a read-only list of transactions to revisit, each with agree, disagree and need-info buttons. ITEMS TO REVISIT READ-ONLY · NO LODGEMENT Transaction · coded twice Transaction · no receipt Transaction · wrong period Transaction · private use AgreeDisagreeNeed info AgreeDisagreeNeed info AgreeDisagreeNeed info AgreeDisagreeNeed info

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. 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.

How we work

A free first call, then three stages.

The first call runs about half an hour and costs nothing. It is often enough to say whether the work is worth pursuing. After that, you decide at each stage.

Stage 1 · From $1,500 + GST

Scope and feasibility

We map the workflow as it actually runs, test the parts most likely to break, and come back with a written scope and a firm price. If the proposed work is not worthwhile, we explain why before you commit to a build.

The fee is set by how many workflows and systems are in scope.

Stage 2 · Fixed price, locked after Stage 1

Build and launch

Built, tested against your real data, and handed over with your team trained on it. Priced against the agreed scope, not against hours. If the build takes longer than we thought, that is our problem. If you change the scope, you hear the cost before we start the work.

Stage 3 · Monthly

Run and improve

Suppliers change formats, regulators change rules, AI models change behaviour. Monthly support covers the maintenance and changes agreed in the support plan; additional work is scoped and priced separately. Scope, fees, notice periods and handover arrangements are agreed before support starts.

Your data and the handover

Built so you can leave.

We agree how you can access and export your data, and how the system would be handed over, before anything is built.

Your accounts, your billing
Hosting, domains and third-party services sit under your own accounts and your own card wherever it is practical. If we part ways, the accounts stay where they are and we transfer access with the configuration and documentation needed to keep the system running.
What the proposal states
The proposal sets out access to the custom code, data and hosting accounts, any third-party licences, and the handover arrangements. It also names who defines the scope, who develops the software and who reviews delivery.
Your AI provider account
Where an external AI service is used, we agree account ownership, billing and data settings with you before launch. If we cannot state how accurate something is on your data, it does not go into production.
Never pooled, never resold
We do not aggregate data across clients, we do not sell it, and we do not build products out of what we see inside your business.

Contact

Start with the problem, not the technology.

Tell us what is taking too long, breaking too often, or costing too much to check. We usually reply within one business day to arrange the initial call.

Direct

info@praxisarc.com.au

Praxis Arc Pty Ltd  ·  ABN 44 700 059 025  ·  Perth WA

The initial call is free. Paid scoping starts only after you approve what it covers and what it costs.