Sketch your stack. See the questions that matter.
Choose the areas your project touches, like ERP, mobile, AI, and integrations, and see the dependencies and discovery questions that decide how big it really is.
Planning workbench // No delivery estimate
Sketch the system surface area
Select the parts involved to create a discussion map. This tool surfaces dependencies and discovery questions; it does not predict project duration or cost.
Current sketch
2 system areas
2 integrations · 1 data source
Questions to take into discovery
- Which system owns each important business record?
- How should retries, duplicate events, and failures be reconciled?
- What does a successful first release need to prove?
Questions, not quotes
Timelines depend on data quality, integrations, and how quickly decisions are made. The estimator deliberately gives no timeline or cost; it shows what needs answering first.
How the questions are chosen
Every map also asks what a successful first release needs to prove.
| When you select | You'll be asked |
|---|---|
| ERP or data migration | Which system owns each important business record? |
| Mobile or offline work | What must users be able to do without connectivity? |
| AI or documents | Which results require review before they affect a business record? |
| Cloud or infrastructure | Who owns backup checks, alerts, and recovery steps? |
| One or more integrations | How should retries, duplicate events, and failures be reconciled? |
| More than one data source | How will data definitions and quality be aligned across sources? |
Why these questions decide the size of a project
Most project overruns come from a small set of unanswered questions: two systems both believing they own the customer record, an offline requirement discovered late, an AI feature with no agreed review step, or integrations that fail silently. Each one can add weeks once a project is underway, and each one is cheap to answer at the start.
Use the map as an agenda. Bring the questions to your team, note who can answer each one, and you will walk into any discovery conversation, with us or anyone else, already ahead.
Using the map
Step 01
Select the areas
Tick every area the project touches, even the ones that feel minor.
Step 02
Count integrations and sources
Include spreadsheets and manual exports; they count too.
Step 03
Answer what you can
Write down answers and owners for each question.
Step 04
Bring the rest to discovery
Unanswered questions become the discovery agenda.
What usually changes the size of a project
Two projects that look identical on a feature list can differ several times over in effort. The difference is usually in the parts that don't show in a demo: how messy the existing data is, how many systems need to stay in sync, how strict the access rules are, and how much of the old system must keep running during the change.
The estimator surfaces those questions so you can answer them before anyone quotes. Clear answers make estimates tighter and projects calmer.
Questions to answer before asking for a quote
- Which systems must exchange data, and in which direction?
- Who owns each piece of data when systems disagree?
- How much historical data needs to move?
- Which workflows can change, and which must stay as they are?
- What happens if the new system is unavailable for an hour?
From map to discovery
The map is a conversation starter. In a discovery phase, each question it raises becomes a short piece of work with an owner: a data sample to review, an API to test, a workflow to walk through with the people who do it. That's how an estimate stops being a guess.
Frequently asked questions
Why doesn't it give a timeline?
Can I share the result?
Does it include costs?
Is anything I select sent to you?
Can I use it for a project with another partner?
What if I don't know the answer to a question?
Keep exploring
How we work
How we deliver software projects: discovery sprint, written specification, two-week sprints with demos, testing, launch, and support.
TechnologyTech stack & standards
The technologies we use across ERP, web, mobile, AI, and infrastructure, and the engineering standards every project follows.
ContactContact
Talk to Anvexis Stack about Odoo ERP, AI automation, web and mobile apps, or cloud infrastructure. A real engineer replies.
Next step
Got a tangled system? Let's untangle it together.
Thirty minutes with an engineer, no slide deck required. You'll leave with a clearer picture, whether or not we work together.
