Custom software
Solution registry Product
A scope you can accept before build hours are spent
Internal tools and a first product release, with discovery priced before product code starts.
Patch · v4
- 01
- Written scope before build
- 02
- Application design for the agreed workflow
- 03
- Implementation and review
- 04
- Access and environment handover
- 05
- Release notes
- 06
- A recommended next block, if you want one
Flux · v3
01 Discover
Map the workflow, the users, and what is out of scope for this release.
02 Plan
A written scope, a sequence, and the hour block for the build.
03 Build
Implement the agreed release and review it against the scope.
04 Release
Handover, access, and a note on what the next block would cover.
Grid · v2
| 01 | A scope you can accept before build hours are spent |
|---|---|
| 02 | Software your team uses in the real workflow, not a demo |
| 03 | A release you can put in front of staff or early customers |
Approach on this lane
Names from the catalog scope for this lane:
- Written scope before build
- Application design for the agreed workflow
- Implementation and review
- Access and environment handover
- Release notes
- A recommended next block, if you want one
Custom software at Coplost Services is a written scope, then a build. Discovery produces the boundaries, the risks, and a plan you can accept or stop. A business application is an internal tool your staff use every week. A SaaS MVP is the first release of a product you intend to sell.
We do not start a build from a slide. The hour block for discovery is separate from the hour block for the build, so you can pause between them.
Hour packs tied to this service track
Hourly rates. A month is the hourly rate times 30.
Discovery
A software idea that is real, but not yet bounded.
Business application
Operations, finance, or delivery teams replacing a manual process.
SaaS MVP
Founders who need a first release, not a full platform.
Questions on this lane
Is a SaaS MVP a full platform?
No. It is the first sellable release: the core job, accounts, and enough visibility to see if the job is used. A platform is a later block, if the first release earned it.
Can discovery and the build be one purchase?
They are two lines so the second can be declined. We can write them in one scope if you already know you want both, and the scope will still show them as separate blocks of hours.
Do you replace our database?
Only if the scope says the new tool owns that record. Otherwise we read from the system that already does.