See Esan in action

An app for the sales reps' phones: pick the customer and the products, and it applies the price list in force, that customer's discount and VAT and prints the quote as a PDF on the company's own template. A rep can raise the discount to 15%; past that, no PDF until Maite approves. Esan builds it, checks it reproduces an issued quote to the cent, publishes it with a QR code, then puts a 4% price rise live.

A quarter of supplier invoices, 150 PDFs with every supplier in its own format, the price lists agreed with each one and the warehouse receipts from the ERP. Until now only the totals were checked. Esan reads all 974 lines against the price in force that day, the discounts, the freight terms and what actually arrived, and finds thirteen overcharges at four suppliers: €2,535.44 before VAT, from 200 kg billed and never delivered to a delivery note invoiced twice. It leaves an Excel with the proof of every case and a claim to each supplier as a draft in Outlook.

A factory in Bergara with 2,400 m² of south-facing roof, a year of electricity use and shifts from 6:00 to 22:00 on weekdays. Esan opens PVGIS, the European Commission's solar tool, in a browser, puts the building on the map, runs the numbers and downloads five years of hourly production. It crosses them hour by hour with the shifts, sizes the system at 200 kWp with nothing exported to the grid, prices it at today's market and delivers a five-page PDF with a source for every figure: €23,470 saved a year, paid back in about seven.

A customer writes to the project's address for twenty jerrycans of "the degreaser from last time", hydraulic oil and floor paint. Esan reads the catalogue, the price list, the customer's terms and their order history, sees that "last time" could be two products, quotes the latest and flags it, works out the 12% discount, the free delivery and the VAT in code, fills in the company's own template and leaves the reply, PDF attached, as a draft nobody has sent.

Esan contacts the other person's assistant and the two of them settle it between themselves: a slot that suits both diaries, a restaurant halfway between the two offices, and a dietary restriction nobody put in the prompt. Esan then opens the restaurant's site, fills in the booking form, and goes back to the other assistant with the reference the confirmation screen gave it.

Two errands before a quarter-close celebration. The pen shop speaks Shopify's agent protocol, so Esan searches it and builds a cart directly. The bakery has no API at all, so Esan opens a browser, finds the cake, fills the order and picks the collection slot, then stops at the terms checkbox and hands over the live page, because that box is the owner's to tick. One click later it carries on in the same session and reads back the confirmation number. The cake is real.

A Stripe export with repeated headers, decimal separators that swap convention mid-file and customers whose emails differ only in case. Esan cleans it, splits the quarter's churn between the customers who left and the ones who downgraded, and proves the split against an MRR bridge that closes to zero. Then it reports what it found on the way: one of those duplicate emails is not a duplicate, and the company behind it has been paying for two plans since January.

Five pricing rules tangled in one sentence become a calculator a rep opens on their phone mid-call. Esan publishes it to a permanent address, then checks its own tier maths in code rather than trusting the page it just wrote. When the rules change from flat tiers to marginal ones it reopens that same file, rewrites the model and the design, and republishes to the same link.

Fifty-five pages of council tender, six of them a scan with no text layer at all. Esan reads the whole thing rather than the parts the questions name, OCRs the annex nobody opens, and answers what was asked with a page citation for each fact. Then it opens the certificate sitting beside the tender, which nobody mentioned, and works out that a clause buried in the scan puts the bid 247 days short of a condition that cannot be cured, days before it was due to go out.

A thirty-seven-minute design meeting and one paragraph from the owner: decisions at the top, then who owes what by when, then the questions that got asked and nobody answered. Esan transcribes the recording, writes the minutes in that shape and turns the paragraph into a skill so it never has to be explained again. Handed the afternoon's recording with four words and no instructions, it produces the same minutes, and finds a decision resting on a question the room deferred and never came back to.

A board meeting tomorrow, one question the owner cannot answer, and eight slides due by morning. Esan compares monday.com, Asana and Wrike against their own pricing pages a year apart, sourcing every figure to a dated archive rather than to a search result. It finds a 44% rise on monday.com, the number the board wants, works out that it is a currency conversion rather than a price change, and throws it away.

A weekend of email: an overdue invoice, a bounced direct debit, a delivery nobody is booked to sign for, a quote a client wants before her board meets. Esan reads the twelve that arrived, files eight jobs in Todoist and touches nothing in Gmail. Then it reports what the list does not show: three of those mails are the same supplier and may be one debt arriving twice. Handed the task for every Monday, it schedules it and lays out everything else already running on the account.