Business Model
Pacala is a software-as-a-service platform. Users subscribe to access it. No hardware, no installation, no specialist setup — it runs on any device with a browser.
The subscription unit is called a Desktop: one instance of Pacala for one operational site. A Desktop is priced per site, not per person, which means a farm with a crew doesn't face a bill that scales with every additional worker. The base subscription includes a set of active user seats, storage, and data transfer.
On top of the base subscription, users activate Extensions: modular add-ons that expand Pacala's capability. Integrations with accounting platforms like Xero, advanced workflow tools, export templates, and more. Extensions are managed within the app. Nobody pays for features they don't use.
This structure does two things: it keeps the entry point accessible for small operations, and it creates natural revenue growth as users expand their use of the platform — without requiring them to move to a more expensive tier.
The market
The problem Pacala solves has a known cost. Research across frontline industries puts the annual productivity loss from information friction — workers searching for context they should already have, redoing work from bad instructions, waiting on a reply before they can act — at over $80 billion globally. Per worker, that averages nearly ten full workweeks a year. Not lost to absence, but to the gap between what people know and what they need to know to act.
Agriculture is the launch market. It is the environment Pacala was built in and the community it is being released to first. But the same core product, with no modification, serves horticulture, construction, events, and any sector where work happens in a physical space and the plan needs to move between the field and the office. The revenue model does not depend on agriculture being the only market.
The adoption model
Pacala is designed worker-first. The field worker benefits personally and immediately from using it — not because they were told to, and not because there is a training programme. Because the tool makes the job easier.
When the tool makes the worker's day easier, they use it. When they use it, the office gets the data. That loop — worker utility driving management visibility — is what makes adoption sustainable. It does not depend on a mandate, a rollout plan, or ongoing IT support.
The demo is the sales tool. A user who has spent time in the demo and understood that it works is a user who already knows the product before they ever speak to anyone at Pacala.
The business
Pacala is pre-revenue, bootstrapped, and founder-led. No external funding. No debt. Development completed over eighteen months using AI-assisted tools.
The operational model is designed to be profitable before it scales: a strict cap on operational expenses as a percentage of revenue from the first paying customer, a founder salary that covers costs without requiring growth to justify it, and a reinvestment strategy focused on building the Extension library and the user base before adding headcount.
Recurring subscription revenue provides predictability. The modular Extension model means revenue per user grows as the platform matures, without constant new acquisition to drive that growth.
The founding user cohort being built at Fieldays 2026 is the first stage of commercial validation. Beta participants provide the feedback loop that shapes the product before public launch. The Launch Waitlist represents the addressable audience for the commercial release.