Offer 01Reporting

AI reporting sprint

Ask about sales, margin or stock in plain words and get the table back, with the query and rows shown.

Start a conversation See what you get
A wholesale warehouse with tall racks of packaged food and drinks, and pallets of stock in the aisles below

Who it’s for

This sprint is for the owner of a $5M to $50M manufacturer, food and beverage producer or wholesale distributor in Ontario or Quebec. It is also for the controller who keeps the numbers. Many of these owners bought the business recently, took it over from a parent or run it for a private equity firm.

Your ERP’s standard reports answer the questions its designers expected. Your questions cut across them: sales against last year by customer, late orders by supplier, margin by product line. Today someone exports two or three lists into Excel, matches them by hand and rebuilds the same report the next month. When that person is busy, the question waits.

The sprint fits when:

  • A report you need every month is rebuilt by hand in a spreadsheet.
  • Two people bring different numbers for the same thing to the same meeting.
  • You took over the business and want its numbers without waiting on one person.

What you get

01One reporting databaseYour ERP and accounting records, copied read-only into a database that belongs to your company and refreshed on a schedule.
02Written definitionsWhat counts as a sale, which date makes an order late and how credit notes count, agreed with your controller.
03Answers on requestYou and your controller ask in plain words. Each answer comes back as a table with the restated question, the query and the rows it used.
04Your manual reports, rebuiltThe reports your team rebuilds most often, chosen with you in week one and set to run on request.
05A test setQuestions with known answers, rerun after every change, so a number that was right stays right.
06Access by personCost and margin figures stay with the people you choose.
07A handoverHow to ask, how to check an answer and who keeps the definitions current.

How it runs

Four weeks from the first call to daily use.

Week 1Your records in one database, and the list of reports to rebuildWe connect read-only to your ERP and accounting system and copy the records into the reporting database. With your controller, we list the reports rebuilt by hand and write the first definitions.
Week 2The first reports, checked against your own booksWe rebuild the chosen reports and tie each total to a figure your controller trusts, such as the income statement.
Week 3Answers on request, with access set for each personYou and your controller ask your own questions. Where an answer looks wrong, we fix the definition or the data behind it, and we set who sees what.
Week 4A reporting setup your team runs, and a decision on what comes nextWe write the test set, schedule the refresh and hand over. Then we review the four weeks with you and decide together whether stage two is worth doing.

The first stage takes four weeks, at a fixed price agreed before work starts. It runs on your own workspace, and if you stop there, everything built in it is yours to keep.

What we need from you

AccessA read-only login to your ERP and accounting system, or scheduled exports where a direct read is not possible. Nothing in the live systems changes.
DataSales, invoice, credit note, purchasing and stock records, plus the spreadsheets behind the reports your team builds by hand.
TimeYour controller for about two hours in week one to agree the definitions, then about an hour a week to check numbers. You bring the questions you want answered.

What changes

You get answers when you ask, instead of waiting for the next spreadsheet. Your controller stops rebuilding the same report every month and spends that time checking numbers.

Two people who ask the same question get the same answer, because the definitions are written down. Every number traces back to the rows behind it, so a figure that looks wrong can be checked against its source.

After week 4

The reporting database keeps running as your workspace, and every module you add reads from it.

Modules
ReportingMargin and pricingQuotingOrder deskClaude on your data
Your workspace
One database with your data and your definitionsDesigned to run on its own server in Canada. A chat answers from it and shows the query.
Your systems
ERPAccountingEmailSpreadsheetsFiles and drawings

Each offer adds one module. The modules share one database and one set of definitions, so each new one starts from data that is already clean. If you stop, what was built is yours.

What can come next

After week 4 the answers stay current as new data arrives from your systems. The database and its written definitions become your workspace, so the next module, such as margin and pricing or quoting, starts from data that is already clean.

  • A weekly pack for you and your board, built from the same database.
  • More sources, such as the rebate spreadsheet, the CRM or the shipping system.
  • Dashboards that stay current, and alerts when a number moves outside a range you set.
  • Margin by product, customer and channel, which the margin and pricing intelligence offer covers.

Questions people ask

What does it cost?
The first stage is a fixed price agreed before work starts, based on the job. ThriveAI does not publish rates.
Do we need to replace our ERP?
No. The sprint reads the ERP you run, including older versions installed on your own server, and every connection only reads data.
How do we know a number is right?
Each answer shows the restated question, the query and the rows it used. Each report is tied to a figure your controller already trusts, and the test set reruns known questions after every change.
Who can see cost and margin?
The people you choose. Access is set person by person in week three, and your controller can change it after the handover.
Where does our data go?
The platform is designed to keep each client’s data on its own server in Canada. You choose a model on that server or a hosted model under a written zero data retention agreement. A hosted model may process requests outside Canada. For the options, see private AI for business.
What if we stop after four weeks?
You keep everything built in the first stage: the database, the definitions, the reports and the test set. It runs on your own systems.

Contact

Name the report you rebuild every month

Tell Derik which ERP and accounting system you run and which report your team rebuilds by hand. He will tell you what a four-week reporting sprint would cover.

Prefer to talk? Book a meeting.

Your message goes to Derik Lawlis, the founder.