Three Services, Each at a Different Stage of the Journey
Understand your options first. Build when ready. Tend what you have built. Each service is complete in itself, and each prepares you naturally for the next step if you choose it.
Back to HomeHow We Think About Integration Work
Most integration projects fail not because of technical difficulty but because they skip the assessment phase — assumptions are made, connections are built without a full picture of the existing system, and problems surface after delivery.
At Mali Compute, we treat each stage as its own contained piece of work. An assessment is not a sales lead-in — it produces a document you own. A build has a defined scope and a tested outcome. A tending retainer has a named person and a monthly report.
This structure means you are never committed further than you have agreed to go.
Link Assessment
A gentle technical review of where AI services could be connected to your tools dependably. We examine one to two of your existing systems, identify viable connection points, and present a tidy set of written options. The decision about what to do next rests entirely with you.
What's included:
- Review of one to two existing systems
- Written options report (PDF, yours to keep)
- Notes on feasibility, risk, and estimated effort
- Follow-up call to walk through the report
- No obligation to proceed further
Process:
- 1 Initial conversation about your systems and needs
- 2 Technical review (approximately one week)
- 3 Options report delivered in writing
- 4 Walkthrough call to answer questions
Connected Build
We build the integration that links a chosen AI service to your software, arranged neatly for reliability and easy upkeep. The build follows a defined scope agreed at the start, includes full testing, and ends with a handover that includes documentation written for the person who will maintain the system.
What's included:
- Scope document agreed before work begins
- Integration built and tested by a named engineer
- Edge case and failure testing included
- Readable handover documentation
- Handover walkthrough call
Process (approx. five weeks):
- 1 Scope definition and agreement (week 1)
- 2 Build phase (weeks 2–4)
- 3 Testing and documentation (week 4–5)
- 4 Handover and walkthrough (end of week 5)
Tending Service
Ongoing care for your integrations, kept tidy and extended gently as needs grow. This is a monthly retainer that gives you a named engineer, regular status reports, and the confidence that someone is watching what you have built. Small extensions to scope can be handled within the same retainer.
What's included each month:
- Named engineer for the duration of the retainer
- Monthly plain-language health report
- Proactive monitoring of upstream AI service changes
- Adjustments as needed for minor changes
- Small scope extensions within retainer hours
How it works:
- 1 Onboarding review of existing integrations
- 2 Monthly monitoring and adjustment
- 3 Report delivered each month
- 4 Renewal or cancellation each month, no lock-in
Which Solution Fits Your Situation?
Not sure where to begin? This comparison should help you identify the right starting point.
| Feature | Link Assessment | Connected Build | Tending Service |
|---|---|---|---|
| Written options report | – | – | |
| Full integration built | – | – | |
| Handover documentation | – | – | |
| Named engineer | |||
| Monthly health report | – | – | |
| Ongoing adjustments | – | – | |
| Starting from | ฿4,400 | ฿9,800 | ฿16,700/mo |
Start with Link Assessment if…
You're curious about AI integration but haven't decided on an approach yet. The report gives you a clear picture without commitment.
Choose Connected Build if…
You know what you want to connect and are ready to proceed. Works best after an assessment, but can also follow your own internal evaluation.
Consider Tending Service if…
You have integrations in use that benefit from continued attention and small improvements over time. Month-to-month, no lock-in.
Shared Across All Services
Real-Condition Testing
Integrations are tested against conditions that reflect actual usage, not just a development environment.
PDPA-Aware Design
Data handling is considered at design time. We follow practices aligned with Thailand's Personal Data Protection Act.
Plain-Language Documentation
All deliverables include documentation written for the person who will use them, not for another developer.
Upstream Change Awareness
We monitor AI service API updates and factor known change patterns into the design of every integration.
Single Responsible Engineer
One named engineer per engagement. No handoffs, no anonymous support queues.
Scope Agreement First
Work does not begin until scope has been agreed in writing. No surprises at delivery or at invoice time.
Clear Prices, Published
- Systems review (1–2 systems)
- Written options report
- Follow-up walkthrough call
- No obligation to proceed
- Agreed scope and timeline
- Integration built and tested
- Handover documentation
- ~5 weeks to delivery
- Named engineer assigned
- Monthly health report
- Ongoing adjustments included
- Month-to-month, no lock-in
Not Sure Which to Start With?
Send us a message with a brief description of your situation. We'll suggest the most sensible starting point without any pressure.
Contact Us