Contact
Talk to an engineer
The first conversation is a call with an engineer about your ERP and the three workflows that hurt most. There is no form to fill in: write to us by email.
01 What happens
What happens when you write
The way in is an email, then a call. What happens after the call is your decision.
-
You send an email
Write to gokusahin@gmail.com. Tell us which ERP you run and the three workflows that hurt most. A few lines are enough.
-
You talk to an engineer
The first conversation is a call with an engineer about those two things: your ERP and the three workflows. That is the whole of it.
-
You decide whether to go further
If you do, the first stage is the Discovery Sprint: 2 forward-deployed engineers, 2 weeks on site. It costs $25,000 fixed fee, and you keep everything it produces whether or not you continue.
02 What to bring
Two things to bring to the call
You do not need to prepare anything else. Both fit in the email.
01
Your ERP
Which ERP you run, and what sits beside it: the spreadsheets, the shared inboxes, the EDI. If there is no usable ERP, say so.
02
The three workflows that hurt most
The ones where the hours go, or where an error costs you. For example: sales order entry from emailed purchase orders, supplier follow-up, AP invoice matching, quoting, returns.
Worth knowing, not required
An engagement needs a sponsor who owns operations, and an IT manager or ERP administrator who can grant read access to the ERP data. If you know who they would be, say so.
Not needed for the call
- A requirements document
- A decision about your ERP. It stays the system of record.
- A commitment to all three stages. You can stop after any.
Before you write
Read how an engagement works.
Three stages, public prices, and you can stop after any.