Project scope and ongoing responsibility
Clear scope first. No surprise software commitments.
A focused website, a small integration, and a multi-user operational system are different projects. Soultware defines the work and the operating responsibilities before development is authorized.
What affects cost and delivery time?
The estimate follows the work the system must handle, the people using it, the constraints involved, and what must be ready at handover.
- Number of workflows, user roles, and approval paths
- Integration interfaces, access, and failure handling
- Data condition, file handling, and migration needs
- Security, privacy, and operational criticality
- Content readiness, pages, and language scope for websites
- Testing, handover, hosting, and support expectations
What does the proposal define?
Before a build starts, you can review the proposed scope, estimate, dependencies, and responsibilities.
- Included deliverables and explicit exclusions
- Cost and timing estimates with assumptions and dependencies
- Milestones, review points, payment stages, and acceptance criteria
- Change handling and responsibilities on both sides
There is no single price or timeline that fits every custom system. Any estimate states what it assumes and what could change it.
Before development
A conversation can identify the next decision.
An introductory fit call covers the current process, users, tools, and constraints. It is not a promise of a complete workflow audit. If deeper discovery is useful, its deliverables, fee, and timing are agreed separately.
See how we workAfter launch
Name an owner for the system.
The agreement specifies source-code ownership or license, repository and hosting access, credentials, backups, monitoring, maintenance, incident handling, and ongoing fees. Support hours and response times are negotiated for the project. No 24/7 coverage is implied.
Hosting and maintenance are not automatically included indefinitely. The proposal states who operates each service and what support is covered.
When should you not build?
If the work is infrequent, the current spreadsheet or product is reliable, and there is little cost or risk to remove, a custom system may be the wrong investment. We compare keeping, configuring, connecting, and building before recommending custom work.
Compare existing tools and custom softwareWhy there is no universal starting price
A website price depends on pages, content, languages, CMS, integrations, and ongoing support. An internal system also depends on roles, workflow rules, data, and operating requirements. A written proposal is more useful than a number without its exclusions. No website starting price or custom-software range is published here.
Start with one recurring process.
Share what happens today and what it costs the team in time, rework, delay, or risk. No technical specification is required.