Paid discovery
If the systems or scope are unclear, agree a separate discovery scope, deliverables, fee and schedule before starting. Review the findings before deciding on ongoing work.
A defined monthly allowance for ongoing work
For maintenance and improvements that continue after a project, agree a monthly allowance and prioritise the work within it. This is planned delivery, not an on-call helpdesk.
Dublin, IrelandIreland, EU & UKFixed-scope project or monthly-hours retainer
- Scope
- Prioritised within agreed hours
- Commitment
- Agreed in writing
- Billing
- Monthly terms agreed before start
- Availability
- Scheduled service hours; no on-call cover
Who this is for
- You need scheduled website or software maintenance.
- You have a prioritised list of CRM, integration or software improvements.
- You want visibility of the hours used and what remains.
How it works
Monthly hours and priorities
Agree the allowance, request channel, service hours, response expectations and carry-over rule in writing. Approve additional hours before they are used.
Milestone acceptance
For a defined piece of work within the allowance, agree its acceptance criteria and approval process in the statement of work or work order. Keep an account of hours used and decisions made.
User acceptance testing (UAT)
Agree who tests, the test environment, acceptance criteria, review window and how defects are recorded in the statement of work. UAT checks the agreed deliverables, not an undefined list of new features.
Warranty
Define the defect warranty, its duration, exclusions and reporting process in the statement of work before delivery. Distinguish a defect against the accepted scope from a new change request.
Post-delivery handover and support
Agree documentation, access handover, ownership, maintenance responsibilities and any post-delivery support in writing. Ongoing work requires an agreed project or monthly-hours retainer; it is not unlimited or on-call cover.
Out of scope
What a retainer excludes
Large builds are scoped separately. Third-party subscriptions and hosting costs are excluded unless expressly included. Infrastructure support, emergency response and on-call cover are not offered. Carry-over and additional hours require the written terms agreed before work starts.
Your side
What we need from you
One route in for requests rather than four people messaging separately. Access that does not have to be requested each time. A rough priority when more arrives in a month than the hours cover.
A single prioritised request list makes the use of the agreed allowance visible.
Where we stop
Where this stops being the right shape
A large, defined build belongs in a fixed-scope project rather than consuming an open-ended sequence of monthly allowances.
Start with a conversation
Tell us what is slowing you down. Discuss fit, the delivery model and whether paid discovery is needed before committing to work.