GingerOSHow we work with you
Know the whole project before you sign.
Five phases from the first call to go-live, typically 8 to 16 weeks. The first two come before any contract.
- Your process, mapped
- What is in scope
- A clickable prototype
- A requirements meeting
- A fixed-price quote
- Signed scope sheet
- Team named, both sides
- Each MVP, accepted
- Full build, accepted
- Go-live
- A partner that keeps it current
- Just the call
- About 10 sample SKUs
- No access, no install
- Project owner
- Sign-off person
- IT contact
- Test data
- Experts for the answer key
- Go-live sign-off
- ScopeBefore any contract
- How long
- One call
- You get
- Your process, mapped
- What is in scope
- You prepare
- Just the call
- Payment
- None
- PrototypeBefore any contract
- How long
- 3 days + a meeting
- You get
- A clickable prototype
- A requirements meeting
- A fixed-price quote
- You prepare
- About 10 sample SKUs
- No access, no install
- Payment
- None
- Contract signedKickoffAfter signing
- How long
- One meeting
- You get
- Signed scope sheet
- Team named, both sides
- You prepare
- Project owner
- Sign-off person
- IT contact
- Payment
- Deposit
- CreateAfter signing
- How long
- Per theme
- You get
- Each MVP, accepted
- Full build, accepted
- You prepare
- Test data
- Experts for the answer key
- Payment
- Refundable until MVP
- DeployAfter signing
- How long
- Set at kickoff
- You get
- Go-live
- A partner that keeps it current
- You prepare
- Go-live sign-off
- Payment
- Balance, on final acceptance
A Project plan window laid out as one table: the five phases, Scope to Deploy, run as columns, with rows for how long, what you get, what you prepare and payment. A Contract signed line before Kickoff splits Before any contract from After signing.
Priced by the system you need.
A fixed price for the scope you sign, quoted after the Prototype Week. Never by the hour.
What makes it bigger or smaller
- How many themes this round covers
- How many systems it connects to
- How many countries and regulations it covers
How the money moves
A line of steps for how the money moves: quote, deposit at kickoff, then MVP acceptance. If the MVP keeps missing and you are not satisfied, the deposit is refunded in full; if it passes, the balance is paid after final acceptance.
Built in stages. Accepted at each one.
Two phases before any contract, then each theme ships first as an MVP.
Your GingerOS
Agree what is in scope.
- What we do
- Walk through your flow with you: where parts come in, who touches them, where they leave.
- Map the systems it runs on: ERP, PLM, supplier files, broker feeds.
- Mark which regulations apply, country by country.
- Write the requirement list and cross out what is out of scope.
- What you get
- A requirement list in plain words.
- What you prepare
- One call. Nothing to install, nothing to send.
- Who from your side
- You, for the call. Bring anyone who owns a step you want changed.
- Done when
- You agree the requirement list.
- Classify new ERP items, with the reasoning written downReal
- Recheck affected SKUs when a tariff notice landsReal
- Chase supplier origin declarationsReal
- Send the approved code to every brokerReal
- A separate dashboard for each plantNot needed
- File entries for usYour broker files
Illustration with sample data: a draft Requirement list window with six sample requirements, four checked and marked Real and two crossed out: a separate dashboard for each plant, marked Not needed, and filing entries, marked Your broker files.
See your own flow working before any contract.
- What we do
- Build a clickable prototype of your own flow in three days, from about ten of your sample SKUs.
- Use your own step names, countries and forms, so it reads as yours.
- Walk through it with you at a requirements meeting the same week.
- Send a fixed-price quote, and answer your IT’s security review, before any contract.
- What you get
- A prototype you can click through, a requirements meeting, then a fixed-price quote.
- What you prepare
- About ten sample part numbers (SKUs), with whatever documents you have. No system access, nothing to install.
- Who from your side
- You, for the requirements meeting. Bring whoever owns a screen in the prototype, and IT if they want to start the security review.
- Done when
- You have the quote and decide.
- Built from
- 10 sample SKUs
- System access
- None
- Installed
- Nothing
- Next
- Requirements meeting, same week
Illustration with sample data: a window titled Prototype · your flow, marked Day 3, with three outlined screens (Review queue, Supplier change, Exposure view) and four facts: built from 10 sample SKUs, no system access, nothing installed, and a requirements meeting next, the same week.
Sign the scope and name the team.
- What we do
- Split your system into themes, for example Classification, FTA and Import/Export control.
- Agree each theme’s MVP for this round, and the tests it must pass.
- Name our team and write the plan with dates.
- Agree how your data arrives: exports to start, read-only access where IT allows, one system at a time.
- What you get
- The signed scope sheet: the themes and each theme’s MVP. The project team, named on both sides.
- What you prepare
- Names for the three roles, and a sample of the exports you already run.
- Who from your side
- The project owner and the person who signs off, for the kickoff meeting. The IT contact, to agree how the data arrives.
- Done when
- The scope sheet is signed and the deposit is paid.
| Theme | This round’s MVP |
|---|---|
| Classification | New items from your ERP, classified with the reasoning on record |
| FTA | Origin check for one trade agreement |
| Import/Export control | Screen new items before they ship |
Illustration with sample data: a Scope sheet window marked Signed, listing three themes (Classification, FTA, Import/Export control) with this round’s MVP for each, and a Signed by line naming the project owner, with Deposit paid.
Build each theme and accept it against tests agreed up front.
- What we do
- Build the theme’s MVP, the smallest version that does the job, and run the agreed test scenarios against your answer key.
- Fix what fails, then hold MVP acceptance with you.
- Build the rest of the theme and accept it the same way.
- Have our trade advisor review every rule before it goes in.
- What you get
- For each theme, an MVP you accepted, then the full theme you accepted, with the test results on record.
- What you prepare
- Test data, and the product documents that exist: specs, drawings, BOMs.
- Who from your side
- The project owner throughout. Your experts while the answer key is built. Each department only when its step comes up.
- Done when
- Every theme passes final acceptance.
- Classification
- FTA
- Import/Export control
Each step ends in a test you agreed to up front.
Illustration with sample data: a Themes · build path window tracks three themes across four steps (MVP, Accepted, Full build, Accepted); Classification has all four done, FTA is on the full build and Import/Export control is at MVP acceptance.
Go live, then keep improving it as partners.
- What we do
- Take each theme live after your sign-off.
- Plan what to automate next with you, on a regular schedule.
- Keep the models and connectors current, on a schedule agreed with your IT.
- Apply the regulation changes that affect your themes.
- What you get
- Your own GingerOS, live, and a partner that keeps it current.
- What you prepare
- A go-live date that suits your team.
- Who from your side
- The person who signs off, and the IT contact for any field written back to your systems.
- Done when
- Final acceptance is signed and the balance is paid.
- Final acceptanceSigned
- Your GingerOSLive
- Section 232 updateApplied
- What to automate nextPlanning
Illustration with sample data: a Go-live window marked Live, with a checklist that shows final acceptance signed, Your GingerOS live, a Section 232 update applied and what to automate next in planning.
Scroll to walk with Ginger
A side-scrolling scene with five checkpoints, Scope to Deploy, and a Contract signed line before Kickoff, where, as you scroll, Ginger the cat raises flags such as Agreed, Signed and Live. At each stop a window shows that phase’s plan beside a sample deliverable.
Agree on the test before we build.
Your experts set the answer key. The pass line is agreed before anything runs.
- What is accepted
- One theme’s MVP, or the full theme.
- The scenarios
- Built together from your own products, including the hard ones. Some stay sealed until acceptance, so no fix can be tuned to them.
- The answer key
- Your experts confirm the correct result for each scenario.
- The documents
- Whatever product documents exist: specs, drawings, BOMs.
- The pass line
- Agreed in advance, before anything is run.
- Who signs
- Someone on your side signs the result.
Illustration with sample data: a Test plan window for a Classification MVP lists four sample scenarios with answer key codes and GingerOS results. When the test runs, one row misses at first, is fixed and retested, and the score bar fills past the pass line.
Who comes from each side.
Four roles on ours. On yours, three, and one person can hold several.
| Role | Scope | Prototype | Kickoff | Create | Deploy |
|---|---|---|---|---|---|
| GingerControl | |||||
| Trade advisorThe trade expertise. Reviews every rule and builds the answer key with your experts. | Marks the regulations | Puts your rules on screen | Joins the team | Reviews every rule | Applies rule changes |
| Product managerRuns the plan. Your day-to-day contact. | Runs the call | Runs the meeting | Writes the plan | Runs the plan | Plans what is next |
| EngineerBuilds the system and connects it to yours. | Maps your systems | Builds the prototype | Sets up the data flow | Builds each theme | Takes it live |
| SalesPrice and contract. Later, joint marketing and other ways to work together. | Not involved | Sends the quote | Contract, deposit | Not involved | Joint marketing |
| Your side | |||||
| Project ownerOwns the project on your side and makes the calls. | One call | One meeting | One meeting | Throughout | Go-live |
| Sign-offSigns the scope, each MVP acceptance and the final acceptance. | Not involved | Not involved | Signs the scope | Accepts each MVP | Final acceptance |
| IT contactReviews security before you sign, then agrees how the data arrives: exports first, read-only access where you allow it, one system at a time. | Not involved | Security review | Agrees the data flow | One system at a time | Signs off write-back fields |
| Your expertsConfirm the correct result for each test scenario: the answer key. No in-house expert? Our trade advisor proposes it and you confirm it. | Not involved | Not involved | Not involved | Confirm the answer key | Not involved |
| Other departmentsR&D, procurement, sales, logistics, finance or legal: one conversation each, only when their step comes up. | Optional | Not involved | Not involved | When their step comes up | Not involved |
A Project team table with one row per role, grouped into GingerControl and Your side, and one column per phase; each cell says what that role does in that phase, and an empty cell means it is not involved.
Questions before you sign
What is Prototype Week?
Prototype Week is how a GingerOS project starts. After one call about your process, where parts come in, who touches them and where they go next, our engineers build a clickable prototype of your own compliance flow in three days, from about ten of your sample part numbers. The same week, we walk through it with your team, screen by screen, and turn every comment into a requirement. A fixed-price quote follows. It needs no system access, no production data and nothing installed.
Is a three-day prototype just a template?
No. It is built from what you tell us on the call: your own step names, plants, countries and about ten of your sample parts, so it reads as your flow. It is a draft meant to be argued with, not the final design. Its job is to make the first requirements meeting concrete.
Who should join the requirements meeting?
Whoever owns a step in the flow you described. Trade compliance usually leads; IT often joins to see how the data would arrive, and procurement, sales or finance join if the prototype shows their step.
What happens after the requirements meeting?
We turn the meeting into a requirements list and send a fixed-price quote for that scope. You decide whether to go ahead, and the prototype is yours to evaluate and show inside your company either way.
Can we start without IT?
Yes. Scope and the Prototype Week need no system access and nothing installed. Before you sign, we answer your IT’s security review. At kickoff, IT agrees how the data arrives, one system at a time.
Do you need our real data?
For the prototype, about ten sample part numbers, with whatever documents you have. If you want an NDA first, we sign it before you send anything. For the build, the test data and answer key agreed at kickoff, as exports or through access your IT allows.
Is it a fixed price?
Yes. A fixed price for the scope you sign, paid in two parts: a deposit at kickoff and the balance on final acceptance. If you change the scope, the change is quoted before any work on it starts.
What happens if the MVP fails?
We fix what failed and run the agreed scenarios again. If the MVP keeps missing the agreed standard and you are not satisfied, your deposit is refunded in full and the contract ends. How many retests, and over what time, is written into the contract before you sign.
How long does a project take?
Our custom builds have typically run 8 to 16 weeks end to end. The Prototype Week is three days plus a meeting the same week, and the plan at kickoff sets the dates for each theme.
How much of our team’s time does it take?
Three roles carry it on your side: a project owner, the person who signs off and an IT contact. In a smaller company one person can hold more than one. Your experts join to confirm the answer key, and other departments only when their step comes up. The plan at kickoff lists the hours for each person, phase by phase.
What happens after go-live?
We work as partners: we plan what to automate next with you on a regular schedule, keep the models and connectors current, and apply the regulation changes that affect your themes. Any yearly cost for this is in the quote, next to the build price, before you sign.
What goes into the contract?
Who owns what is built, how your records export if you leave and how long they are kept, the liability terms, the number of retests before a refund, and joint marketing, which happens only if you agree. The prototype is yours to evaluate and show inside your company either way.