Prepare organization settings
The configuration guide lists every setting per module and opens with the first-day checklist for a new environment.
Review configurationImplementation ownership
Keep the customer in control of the operating decisions.
The customer knows which records are authoritative, who can approve work, which exceptions matter, and what a successful launch means. BusinessIntents can assist, but the implementation still needs named customer owners for scope, data, testing, training, and acceptance. Clear ownership keeps decisions from disappearing between meetings.
Recommended sequence
Use four checkpoints to make readiness visible.
This is the sequence we recommend for a customer-led rollout. The customer runs it with the guides; the team joins any step where assistance has been agreed.
- 01Customer decision
Define scope and ownership
Select the workflows to implement, name decision-makers, record gaps, and agree what must be true at acceptance.
- 02Customer-led setup
Prepare configuration and data
Work through the first-day checklist: company details, currencies, tax rates, payment methods, document numbering, and employees. Then load master data and any approved adaptation work.
- 03User verification
Test the operating model
Run representative transactions, approvals, exceptions, documents, reports, and access checks with the people who will use them.
- 04Readiness decision
Train, accept, and launch
Resolve blocking findings, confirm ownership, prepare users, approve the launch decision, and share the support route.
Each checkpoint ends with a decision by the customer's project lead: move on, or fix what is open first.
Start from the documentation
Start from documented records and workflows.
The product guides describe every setting, role, and workflow, so the rollout can be planned before anyone configures anything.
Map roles and handoffs
The platform guide explains group permissions, personal and application workspaces, inbox tasks, approvals, statuses, reports, and generated documents.
Review the platformTest complete transactions
Use-case pages follow concrete work from trigger to outcome, giving teams a practical starting point for acceptance scenarios.
Choose a use caseOperating readiness
Treat configuration, data, people, and acceptance as one plan.
A technically available system is not automatically ready for daily work. The launch decision should connect product configuration with responsibilities and verified business outputs.
Configuration readiness
Confirm organization data, active lists, user groups, permissions, workflow states, reports, and document layouts against the agreed scope.
User readiness
Train administrators and end users in English or Bulgarian, then verify that each role can complete the work and recognize exceptions.
Operational readiness
Name owners for launch decisions, open issues, support requests, access changes, data corrections, and post-launch review.
How implementation works
What the customer does, and what the team can do.
The customer leads every implementation. The team answers questions on every plan; configuration by the team, migration, adaptations, integrations, and training are Custom work with a separate quotation.
Implementation stages and deliverables
Four stages: scope, configuration and data, user testing, and launch. The result of each stage is a decision by the customer's project lead: the agreed scope, a configured environment, tested workflows, and the go-live decision.
Customer responsibilities
Name a project lead who takes decisions, an owner for each workflow in scope, an administrator who manages users and settings, and the users who test. Quick decisions shorten the rollout more than anything else.
BusinessIntents assistance
On every plan, the team answers questions about setup and the documented workflows by email. Configuration by the team, data migration, adaptations, integrations, and training sessions are available as Custom work on an agreed scope.
Environments and access
A Standard subscription gives your organization its own environment with a dedicated database in AWS Frankfurt. The shared Free Demo, on sample data, is the place to try out ideas before configuring your own environment. Your administrator decides who gets access by assigning users to groups.
Training and acceptance
Users learn from the guides, use cases, and flow guides, in English and Bulgarian. Live training sessions can be agreed as Custom work. The customer's project lead accepts the result once the agreed workflows have been tested.
Timing and rapid delivery
Duration depends on the number of workflows, how ready your data is, any adaptations or migration, and how quickly decisions are taken. A team that uses the standard workflows without adaptations mainly needs time to complete the configuration checklist and test its workflows.
Go-live and stabilization
The customer chooses the go-live date once the readiness checks pass. From then on, questions and defects go to support at office@codbex.com, and product fixes arrive through updates that are applied automatically.
Implementation hub
Move from the rollout plan to the detailed decisions.
Migration and Support are separate pages because data movement and service commitments each have their own boundaries.
Data readiness
Migration
Plan source data, preparation, transfer, validation, cutover, and ownership.
Open page →Operational assistanceSupport
Review channels, hours, response targets, and how to prepare a request.
Open page →Commercial scopePricing
Review the Free Demo, Standard, and Custom paths.
Open page →Product modelPlatform
Understand the records, roles, workflows, workspaces, and outputs being implemented.
Open page →Implementation questions
Set expectations before work begins.
Who leads a BusinessIntents implementation?
The customer leads the implementation and owns its business decisions. The BusinessIntents team can be contacted for assistance.
How long does implementation take?
Timing depends on scope, data readiness, adaptations, testing, decision availability, and the agreed launch approach. There is no fixed implementation period.
Is assistance available on every plan?
Yes. Customers on every plan can ask the team questions by email. Configuration by the team, migration, adaptations, integrations, and training are Custom work with a separate quotation.
What confirms that the system is ready to launch?
The customer's project lead decides, once these checks pass: company details, numbering, and tax rates are set; users are assigned to the right groups; each workflow in scope has been run end to end, including an approval and a printout; opening data is in place; and every blocking finding is resolved.
Prepare the rollout
Bring one workflow, its owners, and the decisions still open.
Use that scope to separate what the customer can prepare directly from the assistance that needs to be agreed.
Write to office@codbex.com with the workflows you want to start with, the number of users, and whether you need migration or adaptations. The team replies with the next step, and with a quotation where Custom work is needed.