Custom Software Engagement
A discovery-led custom engagement for applications, software, portals, AI systems, and multi-system workflows that cannot be priced responsibly from a generic package.
A discovery-led custom engagement for applications, software, portals, AI systems, and multi-system workflows that cannot be priced responsibly from a generic package.
Best for
Projects whose users, requirements, data, integrations, security, risk, milestones, or operating responsibilities require definition before final pricing.
Typically included
- Discovery, evidence review, and scope definition
- Architecture, experience, data, integration, and delivery planning
- Milestone-based design, development, and validation
- Deployment, documentation, handoff, and support terms defined in the proposal
Not included at this starting price
- Work, features, environments, or integrations outside the written scope
- Third-party fees, licenses, usage, migration, or support not listed in the proposal
- Guaranteed revenue, rankings, adoption, accuracy, regulatory status, or other unsupported outcomes
What Cloudexa needs before work starts
- Business objective, users, current workflow, evidence, and accountable owner
- Representative content, data, records, systems, documents, and exception cases
- Priorities, deadline drivers, budget context, security, privacy, and acceptance expectations
What can change the final proposal
- Requirement uncertainty, discovery depth, roles, workflow, data, and permissions
- Migration, integrations, AI providers, security, performance, availability, and environments
- Testing, deployment, documentation, training, warranty, support, and third-party services
Scope note
A written proposal or statement of work defines deliverables, assumptions, exclusions, dependencies, responsibilities, milestones, acceptance criteria, ownership, and fees.
Typical delivery path
- Resolve the highest-impact uncertainties before committing to implementation
- Define a reviewable first release with acceptance criteria and ownership
- Deliver through visible milestones, validation, documentation, and controlled handoff
After delivery
The agreement explicitly addresses intellectual property, repositories, accounts, data, third-party components, environments, documentation, warranties, and ongoing operation.
Published prices are non-binding planning estimates. Final fees are confirmed in a written proposal. Hosting, licenses, taxes, payment processing, model usage, storage, and other third-party charges are separate unless stated in that proposal.
Frequently asked questions
Why is there no published fixed price?
Custom software cost depends on specific users, workflows, data, integrations, quality, risk, and operating responsibilities that cannot be inferred responsibly.
Can discovery be a separate engagement?
Yes. Discovery can produce a decision-ready scope, architecture, risks, options, and estimate without committing the client to the full build.