Skip to content

Scoping Call

Tell us what is breaking

Thirty minutes, no cost, no pitch. We are going to work out whether your problem is actually a software problem — and often enough it is not.

What happens on the call

We ask what you run today, what is failing, and what you have already tried. You will usually get a provisional view on platform direction before the call ends, along with an honest read on whether your data is in a condition to migrate.

What you will not get is a quote. Anyone who prices an implementation before understanding your data is guessing, and that guess becomes a change request three months later.

Other ways to reach us

Request a scoping call

30 minutes, no pitch. We reply within one working day.

We use this to reply to you. No lists, no sharing, no follow-up sequence.

What to tell us

Partial answers are fine. The more you can cover, the more useful the first call will be.

  • What you run today — including the spreadsheets. Especially the spreadsheets.
  • What specifically is breaking — the symptom, not the diagnosis. "Stock never matches the floor" is more useful than "we need better inventory software".
  • How many people would use the new system, and in which roles.
  • Whether you have already chosen a platform, and what led you there.
  • Any deadline you are working to, and what is driving it.

The last two matter most. They usually decide whether this is a three-week project or a three-month one.

What we will not do

  • Quote before we understand your data. The gap between an early guess and reality always becomes a change request.
  • Recommend a platform we are paid to recommend. We hold no reseller agreements with any vendor.
  • Take the project if you cannot name an internal owner. We would rather lose the work than deliver a system that degrades once we leave.
  • Chase you. One reply, and then it is over to you. No sequences.

How we run projectsWhat implementation covers