Maintenance Agreement (MA)

A 12-month maintenance and support agreement to keep your product stable after launch, with a predictable budget and a pool of hours for fixes and small improvements.

Keep your product stable after launch, without ad-hoc fire drills.

With a predictable pool of support hours, you get a clear channel for requests, faster fixes, and steady improvements that keep the product healthy over time.

MA Plans

Clear pricing for a 12-month engagement, so you know the cost before we start. Each plan is a starting point: we’ll tailor the scope to your goals on a short call.

Start-upTimeline: 12 monthsInvestment: THB 92,000

What's included:

  • Man-hours per year: 48 hours‍
  • Faster response for issues instead of ad-hoc support
  • A predictable yearly maintenance budget
  • A small pool of hours for continuous improvements
EnterpriseTimeline: 12 monthsInvestment: THB 320,000

What's included:

  • Man-hours per year: 288 hours‍
  • A larger pool of hours for continuous improvements
  • Less context switching and faster execution on recurring requests
  • A steady maintenance rhythm to reduce incidents and technical drift

Who this is for

  • Teams that want a reliable maintenance baseline after launch
  • Products that mainly need bug fixes, small enhancements, and regular content/design updates
  • Businesses that want predictable turnaround and a clear support processwant a practical CRO rhythm without heavy ongoing overhead

What you get

  • A defined support channel and a clear process for logging and prioritizing requests
  • Faster bug fixes and maintenance tasks within a pre-agreed pool of hours (no ad-hoc negotiation each time)
  • A healthier, more stable product over time through regular fixes, small enhancements, and ongoing housekeeping

Scope

Preliminary application audit

We review the current state of the application and identify key risks and quick stability improvements.

Bug fixes (Criclabs-built)

We support outstanding bugs in work delivered by Criclabs within the agreed scope and hours.

Enhancement, design, and content updates

We use the allocated hours for small enhancements, design updates, and content uploads based on priority.

Server support contact

You have a clear support channel for server-related coordination and incident communication.

Support hours pool

Each tier includes a defined annual hour allocation to use across maintenance tasks.

Out of scope

  • Off-hour support without prior notice (requires 15 days notice; late notice is billed at THB 2,000/hour)
  • Major feature development or large redesigns unless explicitly added
  • Support for third-party codebases not built by CRIC unless explicitly agreed

How it works

1. Kickoff and baseline

Confirm scope, support channels, system access, and priority areas. Run the preliminary audit.

2. Ongoing support rhythm

Log requests, estimate effort against the hour pool, execute, and share status updates.

3. Reporting and planning

Monthly summary of hours used, work completed, and next priorities.

Related work

Projects where we’ve done this work for our clients.

Supporting Honest Bank as they scale a Webflow (Lumos) foundation, improve conversion through UXO, and keep performance stable with maintenance.

Rebuilding LAdV’s luxury Shopify storefront into a faster, clearer shopping journey designed to convert.

Clients come to us for what we do, but they stick with us for how we do it.

2 of 3 project slots open this quarter