Our approach

Pre-launch, and honest about it

Why this exists

Built by someone who has to live with it

Alffi is built and run on Mullinroo Estate, a working mixed operation in New South Wales. Every feature gets used on a real farm, with real stock, real chemical records, and real compliance deadlines — usually within a day or two of being written.

That has a specific consequence: features that look sensible in a spec but are annoying at 6am in the yards do not survive. The platform is shaped by the friction of actually using it, not by a feature comparison against a competitor.

It also means we are not guessing about the problem. Farm software fragments because vendors build for one enterprise type and bolt the rest on. A mixed operation ends up with three subscriptions, three logins, and no single view of the business. That is the problem Alffi is built to solve, and the reason it is a configurable platform rather than another livestock app.

Where we actually are

Early, honest, and moving fast

Alffi is real software running a real operation every day. It is also early — and we would rather you saw exactly where it stands, and where it’s going, from the website than from a demo.

Built and running

  • The web platform — your own records, satellite map, bulk editing, reporting
  • Livestock through to kill batch, carcase feedback and NLIS reconciliation
  • Cropping catalogues with APVMA label lookup
  • Irrigation scheduling driven by soil, crop and evapotranspiration data
  • Equipment, fuel and service history
  • Weather stations, Bureau of Meteorology data and satellite soil moisture
  • Ask Alffi, with every write gated behind your approval
  • Voice on every screen — speak instead of typing, listening for your own paddock and mob names, and read before it sends
  • A phone view of today’s jobs, installable to your home screen
  • Driven against a 75,000-head test herd — cattle, sheep and goats — to find where it bends
  • Public REST API, signed webhooks and MCP access

What’s coming next

  • The mobile app, with offline support. Record a weight or close a job with no signal and let it settle up later. Today there is a phone surface — jobs and Alffi, installable to your home screen — and it needs a connection.
  • eNVD in production. Submission is proven end to end against the Integrity Systems test environment for cattle. We have taken ISC through an integration review and hold their verbal sign-off — signing the licence agreement is what unlocks production. Sheep and goats follow.
  • Markets beyond Australia. We run in Australia today, but much of the internationalisation is already configured for English-speaking markets — metric and imperial units, currency and locale handling are built in rather than retrofitted.
  • Billing. Not switched on. Design partner costs are negotiated directly, and there are no charges in the meantime.

Nothing on this site is a roadmap item dressed up as a feature. If it is described in the present tense, it works today — and what’s coming is listed as what’s coming.

The design partner programme

We are looking for a small number of operations — a handful, not a cohort — to shape the platform while it is still soft enough to be shaped.

What you get

  • No charge during the programme Billing isn’t enabled, and we won’t backdate it. When pricing does start, you’ll get founding terms and plenty of notice.
  • Direct access to the person building it Not a support queue. You describe the problem, and often the fix ships that week.
  • The platform modelled around your operation If your business is put together in a way no farm software can cope with, that is the most interesting thing you can bring us. Fitting the software to it is the product, not a workaround.
  • Your data stays yours Full REST API access and CSV, Excel and PDF export from day one. Nothing you put in is trapped.

What we ask

  • Use it for real work Not an evaluation in a spare tab. The platform only improves against genuine daily use with real consequences.
  • Tell us when it’s wrong Including the small irritations. The friction you stop noticing after a week is exactly what we need to hear about in the first week.
  • Tolerance for rough edges Things will break. Screens will change under you. If that is going to cost you a season, this isn’t the right time to join.
  • Keep your existing records Don’t decommission whatever you use today on our account. Run us alongside it until we’ve earned the switch.

Whether this suits you

We would rather have four partners who fit than forty who don’t.

Probably a good fit

  • Mixed operations that don’t fit neatly into one vendor’s category
  • Businesses whose structure existing software can’t model — shared ownership, agistment, unusual enterprise mixes
  • Anyone already exporting to spreadsheets because the software won’t bend
  • Operations that care about compliance records being audit-ready rather than merely stored
  • People comfortable working from a laptop or tablet in a browser

Probably not, yet

  • You need a native app, or one that keeps working with no signal
  • You work in areas with no reception and need capture that survives being offline
  • You’re outside Australia
  • You need a finished, stable product with a support desk behind it
  • You’re running centre-pivot or lateral-move irrigation as your primary system
  • You need dairy or viticulture specifics right now

How we build

A few commitments that shape the product, and that you can hold us to.

The assistant proposes, you dispose

Alffi’s language model has no write access to your data. It can draft a change and show it to you; only tested, deterministic code can apply one, and only after you approve it. That is an architectural guarantee, not a setting.

What you set up is yours

Add a new kind of record and other software can reach it straight away, over the API and by webhook. We don’t pick and choose which parts of your own data you’re allowed to get at.

Price by business, not by headcount

Alffi doesn’t charge per user or per head. The database is built so a per-seat price cannot be stored — it isn’t a policy we could quietly reverse.

Still interested?

Tell us about your operation and we’ll arrange a walkthrough. No obligation, and no sales process behind it.