Skip to content

Is this a fit?

This page lists the signs that an engagement with our forward-deployed engineers fits your company, the signs that it does not and what to do next.

Your ERP is surrounded by spreadsheets and email

Section titled “Your ERP is surrounded by spreadsheets and email”

The ERP holds the transactions, and the real work happens around it. You will recognize the pattern:

  • Purchase orders arrive as PDFs in the customer service inbox, and someone re-keys them.
  • A buyer tracks late suppliers in Excel, because the ERP report does not show what they need.
  • The schedule lives on a board or in a spreadsheet that someone updates by hand.
  • One person knows how it all fits together, and that person is close to retiring.

It does not matter which ERP sits in the middle. It can be an ERP such as SAP Business One, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Epicor, Infor, Sage, Acumatica, SYSPRO, QuickBooks Enterprise or whatever you run. It stays the system of record.

Fully digital work is work whose inputs and outputs are all digital: emails, documents and ERP transactions. That is the work agents can take on. These are the workflows we look for:

At a manufacturer At a distributor
Sales order entry from emailed purchase orders The order desk: orders by email, EDI and phone
Quoting from requests for quote Pricing and quoting
Purchasing and supplier follow-up Replenishment and supplier follow-up
AP invoice matching AP invoice matching
Production scheduling support Returns
Customer order-status questions Order-status calls

Someone at the top owns operations and wants this done. That is usually the COO or VP of operations, and sometimes the owner or CEO. The sponsor names the workflow owners, sets priorities and clears access. Without a sponsor, decisions stall, and the weekly releases stall with them.

Your size is in the band on the pricing page

Section titled “Your size is in the band on the pricing page”

We work with US manufacturers and wholesale distributors in the size band shown on the pricing page, typically with 100 to 1,500 employees.

Sign Why it does not fit
You want a packaged product There is nothing to license and install. Our engineers build software for your workflows, on site, and that takes their time and some of yours.
We cannot get onto the floor or into the data The work depends on sitting with the people who do it and on read access to the ERP data. Without both there is nothing to build from.
You want a report only The Discovery Sprint produces documents, but they exist to decide what to build. If a report is the goal, this is the wrong engagement.
The work that hurts is mostly physical Agents do not do physical work and do not operate machinery. If the problem is on the line or in the aisles, not in the paperwork around them, we are the wrong help.
  • You have no usable ERP. That can still fit. When there is no usable ERP covers the ERP-like core we build, which you own.
  • You have an ERP partner. That fits. We build what the ERP does not cover and work alongside your partner. See Working with your IT team and ERP partner.
  • You have developers in-house. That fits too. They can take the software over later, and your contract gives you the right to keep running and changing the parts that come from our reusable tooling. See Handover and exit.
  1. Write down which ERP you run and the three workflows that hurt most. The first conversation is a call with an engineer about those two things.
  2. Check the two requirements you cannot work around: a sponsor who owns operations, and an IT manager or ERP administrator who can grant read access to the ERP data.
  3. Read Discovery Sprint to see what the first two weeks ask of your people.
  4. Look at the figures on the pricing page and the terms in Stages and terms.