Why Auxagon
Auxagon is not another farm accounts package. It is the layer that sits on top of the ones you already run and answers a different question: what is coming, and what is it worth to this business?
Accounts packages and farm management software are built to record what has already happened, what was bought, what was sold, what was applied. They are accurate and necessary, and they tell a farmer nothing about the six weeks ahead.
How Auxagon fills it: Auxagon reads live commodity, FX, input-cost and weather signal against the farm's own exposure and maintains a forward view that updates itself.
AHDB prices, Met Office warnings and futures curves are public. Translating a 7% feed wheat move into what it means for one farm's contracted tonnage, storage position and overdraft is a job nobody in a farm SME has time to do weekly.
How Auxagon fills it: Signal is read against the specific enterprise mix, contracted volumes and payment timings the farmer has entered, so the output is farm-specific rather than sector-average.
Most farm SMEs learn about a shortage when a payment fails or the bank calls. The information needed to see it four weeks earlier already exists in the business. It is simply never assembled into a rolling projection.
How Auxagon fills it: A 12-week rolling projection flags the week the balance turns, with the receipts and payments driving it visible underneath.
It is not a replacement for your accounts. It is not a broker, an insurer or a source of regulated financial advice. It does not tell you to hedge, to switch product, or to change your tax position.
Where a question sits inside the FCA regulated advice perimeter, Auxagon names the question clearly and points you to a qualified adviser rather than answering it. That boundary is a design decision, not a limitation we are working around.
