Spreadsheets
Formulas, fields, duplicated work, controls, approvals and reporting logic.
Paid discovery · Business analysis · Functional consulting
Before you spend money building software, know exactly what to build.
Give us your ERP, CRM, spreadsheets, workflows, source code or operating process. We analyse how the business works today, identify the gaps, design the future state, and turn it into a development-ready blueprint your team can build from.
From CAD $4,500 · Fixed scope before work starts · No implementation lock-in · You own the Blueprint.
- Bring
- Excel, Odoo, Salesforce, Sage, code, forms or workflows
- We do
- Current state → gaps → future state → requirements
- You get
- Executive decisions + developer-ready handoff
03Development HandoffUser stories · acceptance criteria · backlog
02Future StateTarget workflow · architecture · integrations
Process→System→Data
01Current StatePeople · process · systems · data · friction
7priority gaps
High impactApproval delays
PriorityP1 · automate
OutcomeBuild with clarity
Best forCEOs, COOs and transformation leads
IndependentPlatform-neutral recommendations
Built forLeadership, operations and developers
Access modelRead-only or controlled discovery
The gap we remove
Stop paying developers to discover the business while they are already building it.
Most expensive software mistakes begin before development starts: the business has one picture of the problem, the implementation team has another, and requirements are still changing after build work has begun.
Nadmaa turns the operation itself into the specification.
Start with what you already have
You do not need a perfect brief.
We can begin from the systems, files and workflows your team already uses. The discovery method changes to fit the evidence available.
ERP / CRM
Odoo, Salesforce, Sage and other systems: configuration, workflows, fit, gaps and integrations.
Custom software
Authorized source repositories, APIs, database structure, business rules and technical debt.
Email & manual work
Shared inboxes, handoffs, approvals, reminders, re-entry and exception handling.
Forms & documents
PDFs, paper forms, contracts, data capture, document routing and signatures.
An idea
If the system does not exist yet, we define the users, journeys, rules, data and build sequence.
Before → Blueprint → After
Move from “we need software” to a buildable operating design.
The Blueprint separates diagnosis from implementation so investment decisions can be made before development cost starts compounding.
The team knows it is painful.
- Excel and email hold critical steps
- Staff re-enter the same data
- Systems do not match the process
- Developers receive changing instructions
- Cost and scope are difficult to predict
The operating model becomes visible.
Inspect→Map→Challenge→Design→Specify
People, process, data, systems, controls and technical constraints are brought into one decision model.
The build team knows what “done” means.
- Future-state workflows are defined
- Requirements have owners and priorities
- Integrations and data movement are explicit
- Acceptance criteria reduce ambiguity
- Implementation can be phased and costed
What you own at the end
Three usable packs. Not one giant BA document.
The exact artifact set is tailored to scope. Leadership gets concise decision material; operations gets the functional model; developers get the detail needed to build and test.
01Executive BlueprintCEO · COO · CFO · Board
Make the investment decision.
Current-state summary, opportunity and waste analysis, future-state vision, priorities, business case, risk register, cost/effort bands and implementation roadmap.
02Functional & Process BlueprintOperations · Product · Managers
Make the operating model explicit.
AS-IS and TO-BE process maps, business rules, fit-gap analysis, roles, permissions, data needs, exceptions, controls and transition requirements.
03Development Handoff PackDevelopers · Architects · QA
Give builders an implementable scope.
Functional/non-functional requirements, user stories, acceptance criteria, architecture, integrations, migration needs, traceability, backlog and UAT approach.
Example artifact library
See what the engagement can produce.
Not every project needs every artifact. We select the documents that remove uncertainty for the specific change you are planning.
Executive Systems Assessment
What is working, what is failing and what deserves attention.
Current-State Process Map
The real AS-IS journey across people, systems and handoffs.
Future-State Process Map
The TO-BE flow with ownership, controls and automation points.
Fit-Gap Matrix
Standard capability vs configuration, customization and integration.
Solution Architecture
The target system landscape, boundaries and major components.
Requirements Catalogue
Business, stakeholder, functional, non-functional and transition needs.
User Stories & Acceptance Criteria
Development-ready behaviours with a shared definition of done.
Integration Catalogue
Systems, triggers, APIs, data exchanged and failure handling.
Data & Migration Plan
Key entities, fields, cleanup, migration and reconciliation needs.
Roles & Permissions Matrix
Who can view, create, approve, change and administer what.
Prioritized Product Backlog
P1/P2/P3 scope sequenced by value, dependency, effort and risk.
Implementation Roadmap
Phases, milestones, dependencies, budget bands and decision gates.
CEO-ready prioritization
Every recommendation should answer: is it worth doing now?
We convert requirements into an investment conversation by rating business impact, effort, risk and priority—not just producing a long list of features.
RecommendationImpactEffortRiskPriority
Automate quote approvalsHighMediumLowP1
Integrate invoicingHighMediumMediumP1
Replace spreadsheet inventoryHighHighMediumP2
Redesign management dashboardMediumLowLowP2
How the engagement works
Inspect the evidence. Design the operation. Then specify the build.
AI can accelerate analysis, but the engagement is led as a functional consulting and business-analysis exercise. Outputs are reviewed against the business context before they become recommendations.
Scope the decision
Agree the workflows, stakeholders, systems, evidence, access model and business outcomes.
Inspect the current state
Interviews plus review of workflows, spreadsheets, configuration, exports, code or data where relevant.
Design the future state
Challenge unnecessary steps, define ownership, controls, automation, integrations and target system behaviour.
Build the handoff
Turn the approved future state into requirements, architecture, backlog, acceptance criteria and roadmap.
Controlled discovery
Analysis should not put production at risk.
Discovery is designed around least-privilege, client-approved access. We can work from exports, sanitized workbooks, controlled environments, read-only databases, approved repositories or system access appropriate to the engagement.
Read-only by defaultNo production write access requiredSanitized data can be usedAccess agreed before discoveryHuman review before recommendations
Fixed-fee discovery
Choose the level of uncertainty you need to remove.
Starting prices are in Canadian dollars. We confirm a fixed scope and fee after the fit call so the boundaries are clear before work begins.
CAD $4,500
Typically ~5 business daysOne bounded workflow, spreadsheet or operational problem with a small stakeholder group.
- Current-state map
- Gap and opportunity analysis
- Future-state workflow
- Core requirements
- Prioritized next steps
Recommended
Business Systems BlueprintCAD $8,500
Typically ~10–15 business daysPrimary system plus up to roughly three key workflows or departments, including a development handoff.
- Executive Blueprint
- Current + future-state maps
- Requirements and fit-gap
- Architecture / integration view
- Backlog + acceptance criteria
- Implementation roadmap
From CAD $15,000
Typically ~3–4 weeksMultiple systems or departments with deeper integration, migration, architecture or codebase discovery.
- Cross-functional discovery
- Detailed architecture
- Integration catalogue
- Data / migration strategy
- Traceability + UAT approach
Exact deliverables depend on the engagement boundary. Implementation is separate. If you choose Nadmaa to implement, the Blueprint becomes the agreed starting point—not unpaid discovery repeated inside the build.
No implementation lock-in
You own the Blueprint.
Build with Nadmaa, give it to your internal technology team, or take it to another implementation partner. The discovery work is valuable even if Nadmaa never writes a line of production code.
Nadmaa Blueprint→Your internal teamNadmaa implementationAnother development partner
Questions
What leaders usually want to know first.
Do we have to know what software we want?
No. That is one reason to do the Blueprint. We start from the operating problem and evidence, then determine whether the right answer is configuration, integration, automation, custom software, process redesign—or no new technology at all.
Can you review Odoo, Salesforce, Sage, Excel or custom software?
Yes. The engagement is platform-neutral and can work across a mixed environment. The scope determines whether we review exports, configuration, repositories, APIs, databases or controlled system access.
Can we use our own developers afterward?
Yes. The Development Handoff Pack is specifically intended to reduce ambiguity for whichever team will build the solution.
Will every package contain every document listed above?
No. The artifact library shows the range. A Focused Blueprint does not need the same depth as a multi-system transformation. We agree the exact deliverables before work begins.
Is the analysis just AI-generated?
No. AI-assisted tools may accelerate code, data or document analysis where appropriate, but the work is framed and reviewed as business analysis and functional consulting. Recommendations are tied back to process, users, controls, data and business outcomes.
What happens after the Blueprint?
You can stop, tender the work, hand it to your internal team, or ask Nadmaa to implement in phases. Either way, you retain the Blueprint and the implementation starts from an agreed scope.
Before the build
Remove the expensive gap between the business and the developers.
Show us how the operation works today. We will help turn it into a future-state design and a development-ready plan before implementation money starts moving.
Book My Free 30-Min Fit Call ↗30-minute fit call · No implementation commitment · Fixed scope before paid discovery starts