RAPID 30 · Business Central
A qualified route to a controlled Business Central first release.
StandardiseOperate
RAPID 30 is InteliSense's accelerated Dynamics 365 Business Central route for organisations whose core finance and operational requirements fit closely with standard Microsoft capability and whose first-release scope can be clearly qualified.
Speed should be earned. Acceleration continues only while the conditions for acceleration remain true.
What RAPID 30 is
A standard-first ERP route with the boundaries agreed before delivery.
RAPID 30 combines qualification, a controlled Business Central first release, fit-to-standard delivery, explicit confidence gates and a clear commercial commitment. The objective is to establish the operational core without letting customisation, data, integrations or unresolved decisions quietly expand the programme.
Qualified scope
The first-release business processes are understood before delivery is committed.
Clear boundaries
Included processes, companies, data, integrations and responsibilities are visible.
Standard first
Business Central capability is used wherever it meets the business requirement.
Confidence gates
Acceleration continues only while the conditions for acceleration remain true.
Shared responsibility
Customer and InteliSense responsibilities are agreed before delivery begins.
Commercial certainty
A fixed delivery fee is agreed for the qualified first-release scope, after qualification.
The outcome
A connected finance and operational foundation.
Business Central brings finance, purchasing, sales, inventory and operational information into one Microsoft platform. Which capabilities belong in the first release is confirmed through qualification.
One finance core
Consistent financial records and controls.
Connected purchasing
Purchasing linked to suppliers, commitments and inventory.
Connected sales
Orders connected to customers, stock and finance.
Inventory visibility
A clearer operational view of stock and movement.
Management information
Operational and financial information from a common platform.
Microsoft ecosystem
Integration potential across Microsoft 365, Power Platform and Power BI.
Could we fit?
A quick read before anything else.
Company size is not the test. Process complexity, readiness and decision velocity matter far more.
Likely fit
- Core finance requirements are clear
- The organisation is willing to standardise
- Sales and purchasing processes are relatively conventional
- Inventory requirements are understood
- The first-release company structure is controlled
- Data owners are available
- Critical integrations are known and contained
- Business users can participate in validation and testing
- Decisions can be made quickly
Requires deeper qualification
- The operating model is still being decided
- Every legacy process is expected to be reproduced
- Manufacturing is highly engineered or dependency heavy
- Warehouse automation is central to the first release
- Several entities need materially different designs
- The integration landscape is large or unresolved
- Data quality or ownership is unknown
- Detailed historic migration is treated as mandatory
- Decisions cannot be made at delivery pace
Nothing on the right is an automatic exclusion. It means the item needs to be understood before it is assumed to fit an accelerated first release.
The first release
What a qualified first release can contain.
This describes a potential operating core, not an automatic bundle. Qualification confirms the actual scope.
Potential first-release scope
Core finance
General ledger, payables, receivables, cash and banking, dimensions, applicable VAT or tax configuration, financial periods, standard financial controls and core reporting. Fixed assets where required and qualified.
Purchasing
Vendors, purchase orders, receipts, purchase invoicing and focused approvals where appropriate.
Sales
Customers, quotes and orders where required, shipments, sales invoicing and standard pricing where appropriate.
Items and inventory
Items, locations, inventory movements, availability and standard replenishment where appropriate.
Reporting
Standard Business Central reporting, role centres and agreed focused Power BI requirements where justified.
Security
User access, permissions and approval authority appropriate to the first release.
Data
Qualified master data, opening balances, agreed open transactions and required reference data.
Requires additional qualification
Manufacturing
Simple, bounded production can potentially qualify. Highly engineered, dependency-heavy or shop-floor-intensive production usually needs a broader route.
Warehousing
Standard inventory and warehouse processes may fit. Automation, specialist scanning, robotics or full WMS capability needs deeper assessment.
Multiple legal entities
Entity count is not the test. What matters is whether processes, localisation, currency, intercompany and reporting genuinely differ.
Integrations
A small number of well-understood integrations can be part of the qualified scope. A large or unresolved landscape can change the route.
Specialist extensions and ISVs
An established extension can accelerate fit. Its licensing, configuration, testing and support implications still need to be understood.
Complex reporting
Business-critical first-release reporting is separated from what can be rationalised or introduced later.
Planning and pricing
Advanced demand, supply or production planning, and bespoke rebate, promotion or contract pricing, need to be qualified before they are assumed.
Historic data
Large volumes of detailed transactional history, poor-quality legacy data or multiple complex sources need a deliberate decision, not an assumption.
Qualification determines whether each item fits the first release, should be simplified, should be deferred, requires an ISV, changes the commercial scope, or needs standard Business Central delivery or Transform instead.
How delivery works
Seven stages, with the decisions visible from the start.
The stages make operating decisions, validation, responsibilities and cutover explicit rather than implied.
Qualify
Confirm fit, first-release scope, complexity, responsibilities and commercial boundaries.
Prepare
Confirm data, users, environments, process owners and critical dependencies.
Validate
Walk representative finance and operational processes before assumptions become embedded.
Configure
Build the qualified Business Central operating model.
Prove
Test critical processes, controls, data, security and integrations.
Cutover
Reconcile opening positions, migrate agreed data and complete go-live readiness.
Operate
Move into live use, adoption, stabilisation and prioritised improvement.
Confidence gates
Acceleration continues only while the conditions for acceleration remain true.
Four gates re-confirm the position before the next stage of investment. A gate is a decision point, not a penalty.
Gate 1
Before commitment
Qualification gate
Establishes whether RAPID 30 is a responsible route before anyone commits to it.
Confirmed at this gate
- Fit to standard
- First-release outcome
- Process complexity
- Company and entity structure
- Critical integrations
- Any material customisation
- Named business ownership
- Commercial boundary
Decision
Proceed · Proceed with conditions · Re-scope · Choose another route
Gate 2
Before accelerated configuration
Readiness gate
Confirms the organisation can sustain the pace before configuration builds momentum.
Confirmed at this gate
- Data owners
- Representative data
- Environments
- Process owners
- Business availability
- Critical dependencies
- Required decisions
Decision
Proceed · Resolve the readiness issue · Pause acceleration
Gate 3
Before cutover
Prove gate
Confirms the business can genuinely operate on the configured model, not just that it was built.
Confirmed at this gate
- Critical scenarios tested
- Data validated
- Finance reconciled where applicable
- Integrations proven
- Security appropriate
- Material defects understood
- Business users ready
Decision
Proceed to cutover · Remediate · Re-plan
Gate 4
Before live operation
Cutover gate
The go or no-go decision, made on evidence rather than momentum.
Confirmed at this gate
- Agreed opening position
- Cutover ownership
- User readiness
- Access
- Operational processes
- Support and stabilisation arrangements
- Unresolved risks understood and accepted
Decision
Go · No-go · Controlled deferral
Shared responsibility
Accelerated ERP requires the business to stay engaged.
A partner cannot create decision velocity on behalf of the customer. Both sides know what they own before delivery begins.
The customer owns
- Executive sponsorship with authority to resolve cross-functional issues
- Finance ownership of design and the opening position
- Operations ownership of sales, purchasing and inventory decisions
- Named data owners and validated source data
- Key users available for validation, testing and adoption
- Timely decisions at delivery pace
- Customer-side cutover ownership
InteliSense owns
- Qualification and honest route recommendation
- First-release scope, boundary and commercial definition
- Business Central configuration of the qualified model
- Migration structure, templates, mapping and loading
- Validation, testing and defect management
- Cutover planning and go-live support
- Stabilisation and prioritised improvement after go-live
Commercial certainty
Qualification first, then the commitment.
The sequence matters: qualification, then agreed scope, then agreed readiness assumptions, then agreed responsibilities, then the commercial commitment. A fixed delivery fee is never offered before the requirement has been qualified.
The delivery fee covers
- The agreed first-release processes
- The agreed company and entity scope
- The agreed data scope
- Explicitly qualified integrations or extensions
- The agreed InteliSense delivery activities
- The agreed delivery fee for that scope
Costed separately
- Microsoft licensing
- Approved ISV or third-party costs
- Customer internal resource
- Additional scope or agreed variations
Fixed fee does not mean unlimited scope.
An integration or extension can sit inside the fixed scope where it was explicitly qualified and agreed. What is not qualified is not silently absorbed.
Change control
A new requirement is assessed, not absorbed.
If something new appears after the first-release scope is agreed, the options stay visible.
- Swap a lower-priority requirement
- Defer the new requirement
- Use standard capability instead
- Introduce an ISV
- Agree a commercial variation
- Change delivery route
If RAPID 30 is not right
The honest recommendation may be a different route.
Qualification can conclude that RAPID 30 fits, fits with conditions, or is the wrong shape. All three are useful answers.
Standard Business Central delivery
The requirement is sound, but the complexity, dependencies or pace need a conventional delivery shape.
Business Central deliveryTransform
The future operating model, standardisation priorities or first-release boundary need defining before a delivery route is chosen.
Explore TransformRecover
An implementation has stalled, overrun, gone live badly or lost stakeholder trust. Establish what is true before starting another delivery.
Explore Recover
After go-live
The first release should create a foundation, not an ending.
Later priorities are based on live operational experience and value rather than assumptions made before the platform was used. None of this is a contractual obligation.
Step 1
Operate
Live use, adoption and day-to-day operational confidence.
Step 2
Stabilise and support
Resolve early issues, embed routines and settle the operational rhythm.
Step 3
Optimise
Refine processes, automation, reporting and adoption using real operational experience.
Step 4
Expand
Add capability where the business case supports it: integration, advanced operations, data and AI.
Where later value tends to come from
Improvement is chosen, not assumed.
- Adoption
- Process optimisation
- Automation
- Power BI and reporting
- Integration
- Additional Business Central capability
- Advanced operations
- Data and AI
- Predictive intelligence
- Continuous improvement
Check the fit
A two-minute read on whether RAPID 30 is a responsible route.
Five short questions. The result is an honest directional signal, not an automated decision, and your answers are carried into the conversation.
Indicative signal
Answer the questions and we will show an honest directional signal. This is not an automated decision: it simply makes the first conversation more useful.
Your answers are carried through, so you will not be asked to repeat them. Final qualification is always a conversation.
Deeper qualification
The detail behind the decision.
Everything below is what qualification actually examines. Open only what matters to you.
Business Central scope
Data and migration
Integrations, ISVs and reporting
Delivery, testing and cutover
Fit-to-standard
The fastest way to make ERP complicated is to rebuild the old system inside the new one.
RAPID 30 asks whether standard Business Central capability supports the required outcome, rather than how to reproduce every existing screen, report and workaround. This does not mean zero customisation: it means justified customisation, understood before it becomes part of the commitment.
Standard where it works
Use standard capability where it meets the business requirement.
Challenge legacy habits
A process is not automatically valuable because the organisation has always done it that way.
Customise for a reason
Where a genuine differentiator requires extension, understand its impact before including it.
Protect the future platform
Unnecessary customisation adds testing, support and future upgrade complexity.
Company size is not the test.
A larger organisation with one legal entity, standard finance and simple inventory may fit RAPID 30 better than a smaller organisation with bespoke manufacturing, complex integrations and highly customised processes.
Qualification looks at
- Process complexity
- Company and entity structure
- Localisation
- Data complexity
- Integration complexity
- Inventory and warehouse complexity
- Manufacturing requirements
- Customisation
- Reporting
- Readiness
- Decision velocity
Microsoft foundation
Business Central within a wider Microsoft platform.
Which technologies apply depends on the qualified first release. This is not a licensing guide or a promise that every capability is included.
Dynamics 365 Business Central
The finance and operations foundation.
Microsoft 365
Familiar working across the Microsoft environment.
Power Platform
Controlled extension where there is a clear requirement.
Power BI
Focused reporting and analysis where justified.
Dataverse
A shared data layer where the qualified design requires it.
Azure integration services
Integration capability where the qualified architecture requires it.
Evidence
Customers talking about working with InteliSense.
These videos are evidence of customers working with InteliSense. They are not presented as RAPID 30 delivery evidence, and none of them should be read as a claim about a particular route, platform scope or delivery duration. Verified RAPID 30 evidence will be published here when it exists.
Customer voice
What customers say about working with us.
Customer voices
InteliSense customers
Hear our customers talk about InteliSense
Common questions
Questions buyers ask about RAPID 30.
Other RAPID routes
A different starting point may suit better.
RAPID 10 and RAPID 90 apply the same qualification thinking to different Microsoft platforms and levels of complexity.
Dynamics 365 CRM / Customer Engagement
RAPID 10
An accelerated route to a working customer engagement foundation where the sales or service process is well understood and close to standard.
Ideal when
- Sales or service process already understood
- Small number of users to onboard first
- Limited integration in the first release
- Decisions can be made quickly
Dynamics 365 Finance & Supply Chain
RAPID 90
A structured accelerated route to an enterprise finance and supply chain core where scope is contained and the organisation can sustain the pace.
Ideal when
- Enterprise scale with a contained first release
- Standardisation is an accepted objective
- Programme governance already in place
- Business availability can be protected
Is the operating core clear enough?
Find out whether your Business Central requirement fits RAPID 30.
We will understand the operating requirement, test whether it fits, define the first-release boundary and make the commercial commitment, responsibilities and dependencies clear before delivery begins.
Not sure RAPID is right? How RAPID works