Users and roles
Identify each user type, permission boundary and approval responsibility.
Scope-based software pricing
Custom software pricing begins with workflow clarity, not a fixed package label.
Two systems with the same name can require very different effort. A CRM for three staff members is not the same as a multi-team platform with permissions, audit logs, migration, mobile access and external integrations. Kailvex prices custom development after mapping the users, workflows, data, exceptions and acceptance criteria that define the real product.
✓ Written scope✓ Transparent limitations✓ Secure handover planning
UnderstandMap users, rules and dependencies
DesignChoose the simplest reliable workflow
BuildDevelop and test the approved scope
HandoverDocument access, ownership and support
Workflow-based scopeMilestone planningTesting and acceptanceSupport separation
What the solution may include
Capabilities selected around the actual operating workflow.
Every feature remains subject to written scope, platform capability, data readiness and third-party approval.
Workflow and exceptions
Document the normal path and the cases that require reversal, reassignment or manual review.
Data model and migration
Define records, history, imports, exports, retention and source-data quality.
Integrations
Estimate payment, messaging, accounting, identity or other external systems separately.
Quality and security depth
Plan testing, audit logs, backups, performance and sector-specific controls.
Delivery model
Choose a focused MVP, phased implementation or full release based on risk and dependency.
Practical outcomes
Reduce operational friction without making unsupported promises.
The goal is a maintainable system that makes responsibilities, statuses and customer expectations easier to understand.
Defensible estimate
Cost is tied to documented features and complexity rather than an arbitrary label.
Prioritised release
Essential workflows can launch before lower-value enhancements.
Clear acceptance
Each milestone has review criteria and approved deliverables.
Visible ongoing cost
Hosting, monitoring, maintenance and future development are not hidden inside the build price.
Delivery approach
Decisions are documented before the system is treated as complete.
Discovery, prototyping, implementation and acceptance are connected to the same approved business rules.
Discovery
Review the problem, current process, users, data and business rules.
Specification
Create screens, workflows, permissions, integrations and acceptance notes.
Commercial plan
Estimate milestones, dependencies, payment stages and ongoing services.
Controlled delivery
Build, demonstrate, test and approve each agreed phase.
Scope and responsibility
Important boundaries to confirm before implementation.
Kailvex documents technical responsibilities, but the customer remains responsible for business policies, lawful operations and information supplied for the project.
- Early estimates change when workflows, users, data or integrations change materially.
- Third-party API access, licence fees and infrastructure are outside Kailvex’s control.
- Regulated workflows may require independent legal, security or compliance review.
- A prototype or MVP should not be presented as production-ready until the agreed testing and deployment work is complete.
Frequently asked
Questions to resolve before approval.
A broad range may be possible, but a reliable quotation requires enough detail about users, workflows, data and integrations.
An MVP reduces initial scope only when the essential workflow is prioritised carefully; it should not omit necessary security or data integrity.
Only if listed in the proposal. Build cost, infrastructure and ongoing support should be shown separately.
Yes. Phased delivery can reduce risk when each phase has a useful outcome and a clear integration path.
Start with clarity
Request a written scope before choosing the implementation path.
Share the users, workflow, data, integrations, deadlines and approval process. Kailvex will identify the practical next step without promising outcomes controlled by third parties.