Plans
Three ways to engage. The third is the most underrated: it lets you start without committing to a build.
Ranges are set in the first conversation, with the scope on the table.
Product licence
One of the systems already built, deployed with the business’s brand, products and rules. The shortest route to production.
Businesses that fit an existing product
On request
- Deployment on the client’s server or on one provided.
- Initial loading of catalogue, suppliers and users.
- Team training, with the interactive tours included in the product.
- Commercial modules switched on by configuration, according to what the business uses.
- The system stays with the client. No commission per sale.
- Development of functionality the product does not have: that is a custom project.
- Data migration from a previous system, quoted separately depending on its state.
- Third-party costs: server, domain, payment gateway and tax certificates.
Implementation time depends on the product: between three and six weeks.
Fixed-scope custom project
Documented scope and a fixed budget agreed before work starts. Built on the proven foundation, with the time spent on what is particular to the business.
Businesses whose own process is the advantage
On request
- Discovery of the full circuit and documentation of what is not written down.
- Scope and acceptance criteria signed off before the first line of code.
- Development on the Suite PYMES foundation, with the standard part already solved.
- Automated tests delivered with the system, to re-run on every change.
- Documentation written so the system can be handed to someone else.
- Scope changes during construction: quoted as a new stage, with their own acceptance criteria.
- Support and evolution after delivery, contracted as monthly hours.
Quoted after discovery. The process audit can be contracted on its own, before deciding on any development.
Monthly support hours
A monthly block of hours for support, adjustments and evolution on a system already running.
Systems already in production
On request
- Incident handling with an agreed response time.
- Configuration, reporting and minor functionality adjustments.
- Dependency updates and periodic security review.
- Unused hours are reported; they are not billed as consumed.
- Development of new modules, taken on as a fixed-scope project.
- Support for third-party systems Entropy neither built nor audited.
The number of hours is adjusted after the first two months, with real usage on the table.
The hard question first: did the business make money last month, or does it look like it did?
If the answer is uncomfortable, there is a fifteen-minute conversation worth having. The system is shown running on a demonstration business, and the way the work happens today gets mapped.