No surprises. Everything written down.
You always know what is being built, what it costs, and what happens after go-live.
Requirement document
Discover
Workshops with the people who do the work. We map today's process and the real gaps.
Signed specification
Specify
Screens, rules, reports and data defined in detail, with an estimate in hours.
Working software
Build
Weekly releases on a test site you can click through.
UAT sign-off
Test
Your users test against written scripts; we fix until every script passes.
Manuals and go-live checklist
Train and go live
Role-based training, data migration and a planned cutover.
Support runbook and AMC
Support
Hypercare after go-live, then annual maintenance.
The six stages
- Discover — workshops with the people who do the work; we map today’s process and the real gaps. Deliverable: business requirement document and process journeys.
- Specify — screens, rules, reports and data defined in detail. Deliverable: functional and technical specifications, effort estimate, signed scope.
- Build — iterative releases on a hosted test environment you can click through every week. Deliverable: working software, release notes.
- Test — your users test against written scripts; we fix until every script passes. Deliverable: test cases, UAT sign-off.
- Train and go live — role-based training, data migration and a planned cutover. Deliverable: user manuals, training guides, go-live checklist.
- Support — hypercare after go-live, then annual maintenance. Deliverable: support runbook, AMC.
Engagement models
| Model | Best for | How it is priced |
|---|---|---|
| Service pack | Enhancements, change requests and ongoing development of any size | Prepaid blocks of 50, 100 or 200 hours, logged task by task (below) |
| Fixed-scope project | A defined module, website or migration | Fixed fee against a signed specification |
| Dedicated team | Ongoing product or ERP roadmap | Monthly fee per role |
| Annual maintenance (AMC) | Systems in production | Annual fee for maintenance and bug fixes |
| Product partnership | Founders building a SaaS product | Agreed case by case |
Service packs
We work transparently on prepaid hour packs: you buy a block of hours, every task is estimated before it starts, and every hour used is logged against the task it was spent on.
Packs come in three sizes — 50, 100 or 200 hours — with larger packs carrying a lower effective rate. Pricing is shared on request with a written proposal.
- 50 hours
- 100 hours
- 200 hours
How a pack works:
- Choose a pack; hours are credited to your account on payment.
- Raise a requirement; we reply with a written estimate in hours before any work begins.
- You approve the estimate; work starts.
- Hours are logged daily against each task, and you see the running balance at any time.
- When the balance runs low, we tell you before it reaches zero — no surprise invoices.
One rate covers every service line: Odoo, software, apps and AI, web, e-commerce, hosting and security work.
Pack terms:
- Pack hours are valid for 180 days from the date of payment.
- Hours unused at the end of 180 days carry over only as AMC hours — usable for maintenance and bug fixes — for a further 365 days.
Support and maintenance
- Code maintenance and bug fixes are covered under an active AMC.
- New features and enhancements are quoted and approved before work starts.
- Every delivery ships with Riamona’s software licence agreement, so usage rights and support terms are clear from day one.
What you always receive
- Source code for your custom modules
- Functional and technical documentation
- Test cases and UAT records
- User manuals and training guides
- A named contact accountable for delivery