A working session, not a demo.
Bring one workflow — the one currently held together by spreadsheets, paper and text messages. Forty-five minutes with someone who has built for operations like yours.
You will leave with three things: whether Genwright is the right tool for that workflow, what a first build would cover, and what it would cost. Including, sometimes, the answer that it is not the right tool.
What we will ask
- Walk us through the workflow the way you would explain it to a new hire.
- Where does it currently break, and who notices first?
- What gets re-keyed from one system into another?
- Who has to sign off, and what does an auditor or customer ask for afterwards?
- What has to keep working — the TMS, the accounting system, the telematics?
No slides required. A photo of the paper form is more useful than a deck.
Request a scoping callOr email mike@knomatic.com with a sentence about the workflow.
From the call to a scoped pilot
- STEP 01
Scoping call
Forty-five minutes. One workflow, in detail, with the people who actually run it.
- STEP 02
Written scope
What the first build covers, what it deliberately does not, the integration surface, and a fixed price. In writing, so it can be circulated internally.
- STEP 03
Pilot build
Typically two to three workflows over about four weeks, run with your team or a certified partner, reviewed in a build environment before it goes near live data.
- STEP 04
Pre-flight and launch
Inspected, then promoted to production at one site or one vessel. Fleet-wide rollout follows a workflow that has already carried real load.
Four weeks is the build. It is not the calendar. Security review, procurement and internal approval usually take longer than the build itself, and we would rather say so now than discover it together in month three. Genwright compresses delivery, not your buying cycle.
Three things that make the call worth more
The artifact, not the description
A photo of the paper form, a screenshot of the spreadsheet, an export of the report someone builds by hand every Monday. The real thing tells us more in a minute than a description does in ten.
Someone who does the work
A superintendent, a safety director, a dispatcher, a foreman. Scope written without them is scope that gets rewritten.
Your integration constraints
What systems must keep working and who owns them. Integration is usually what sets the timeline, so it is better raised on the first call than the fourth.
Before you book
Is this a sales call?
It is a qualification call in both directions. Some workflows do not belong on Genwright — a problem that a packaged product already solves well is one of them — and saying so on the first call costs less than discovering it in month two. Expect a recommendation, including sometimes a recommendation to buy something else.
Do we need budget approved first?
No. Most operations use the call to find out what a first build would cost so they can build a case internally. The written scope that follows is designed to be circulated to whoever approves spend.
Who should be on the call from our side?
Someone who does the work, and someone who can say yes. If those are different people, bring both — scope written without the operator gets rewritten, and scope without the decision-maker sits.
What if we already have something built that is not working?
Bring it. Describing an application built elsewhere is a useful call, because the pre-flight checks are a reasonable inspection framework whether or not the system was built on Genwright. Sometimes the answer is a fix rather than a rebuild.
Can a partner run this instead?
Yes. Channel partners and certified builders run scoping and delivery in their own markets, and for operations outside the United States that is often the better path. Ask on the call and we will point you to the right one.