First Shift
Ten days on your floor. Working software at the end.
Every Kingpost engagement starts here. We pick one problem with you, build Keel around it on your data, and leave it running on a real shift.
The ten days
Before day 1
NDA signed. We agree on the one problem and the exports we need.
Your timeOne-hour call with the owner or GM
Days 1–3
Walk the floor, shadow the people doing the work, pull the exports, map how work actually moves.
Your timePoint person, about two hours a day
Days 4–8
Build the workflow in Keel on your data; test it at the cell with the people who'll use it.
Your timeThe users, about 30 minutes a day
Days 9–10
Run it on a real shift, fix what breaks, hand it over.
Your timeOne-hour readout with the owner
What we need from you
Floor access during working hours, one point person, read access to the exports we ask for, and a place to plug in a laptop.
What you walk away with
One workflow running in Keel, used on a real shift.
Your data, exportable at any time, in formats you can open.
A written scope and fixed price for a Deployment, if you want one.
After First Shift
Deployment: fixed scope, fixed price, agreed before work starts.
Operate: monthly; we run Keel, watch it, and keep improving it.
Price
Scoped on a call. Credited toward a Deployment signed within 30 days.
Questions
- Do we have to replace our ERP?
- No. Keel reads what your ERP exports and works beside it.
- Do you need our IT people?
- Briefly, for read access to exports. Nothing is installed on your network during First Shift unless you ask.
- What if the problem is bigger than ten days?
- First Shift builds the first piece. The Deployment scope covers the rest.
- Will you sign our NDA?
- Yes, before day one.
- Do you follow our safety rules?
- Yes. We bring our own PPE and complete your site training.
- What happens to our data if we stop?
- You get a full export. We delete our copy within 30 days and confirm in writing.