Services
Implementation services
[CONTENT SLOT: S0 lead-in — one short paragraph. State that implementation services exist; do NOT resolve permanent-pillar vs bridge-to-self-serve (D13). Never "Stocktimal requires professional services".]
Onboarding is the hard part
[CONTENT SLOT: S1 — 100-150 words. May ONLY be stated as our own experience ("In our experience..."), never as an industry fact and never with a statistic (N16). Links to /product.]
What we actually do
Four things, in roughly the order they come up.
Configuration and setup
Getting your catalogue, suppliers and sourcing options into the system in a shape that matches how you actually plan — rather than how the data happens to come out of your ERP today.
Automating the routine parts
The uploads and the weekly cycle, so producing a plan stops depending on somebody remembering to do it on a Monday.
Data analysis
Looking at what your history actually says before anyone tunes a parameter. Most of the surprises live here, and they are cheaper to find now than after the first run.
Calibrating the demand models
The part that decides how much buffer a SKU carries. It is also the part we would rather not have you guess at, because a wrong assumption here is expensive in both directions.
None of it is mandatory. Some customers take all four, some take the first and do the rest themselves, and we will tell you which we think you need rather than quoting for all of it by default.
How an engagement runs
It starts with your data, not with a project plan. We look at what you can export and what shape it is in, and that tells us how much of the above is actually needed — which is also what drives the price. From there the work is scoped in writing before it starts.
[OWNER INPUT NEEDED: O-3 follow-up — is there a typical engagement SHAPE and rough DURATION you are willing to state (fixed-scope vs T&M, weeks vs months)? 'Deliberately vague' is a valid answer and this section stands without it. Diagram D3 stays omitted either way.]
The honest boundary
We do not run ERP integration projects, and we do not do S&OP process consulting. The more useful limit is the third one: we do not intend to be your data team indefinitely. The mapping work exists so that your own people can rerun it next quarter without calling us — if you are still dependent on us a year in, we have done the engagement badly.
[CONTENT SLOT: S4 — 80-120 words. The body above is scaffold prose resting on C2, C14 and D13.]
What this page is, and is not
This describes how we typically work with early customers. It is indicative, not a scope of work. Any engagement is defined in a written proposal.
Talk to us about an implementation
[CONTENT SLOT: S5 — 40 words leading into the single primary CTA.]