Custom business software & AI agents in MalaysiaOne business.One shared picture.
We work alongside your team to turn disconnected tools or a promising AI prototype into a working business system. Our forward deployed engineering covers discovery, custom software, integrations and rollout—with your team in control of important decisions.
Running costs may apply. Eligibility & terms
Kuching, Malaysia · Working with teams worldwide
A promising prototype.
Useful to one person. Hard to share safely.
This says the job is open.
A separate copy of the operating picture.
“I already updated that.”
The update lives in another conversation.
What is actually waiting?
First, someone has to piece it all together.
Which version is right?
Concept example · sample business and records
The prototype works. The team is still guessing.
The owner has a useful local tool. Everyone else has their own file, message thread or version of the same job.
Your business stops depending on one person’s files and memory.
From a real build / Clinic operations
83% less
estimated reduction in daily administration
About 3 hours down to under 30 minutes
Build file 01
Clinic Operating System
A private workspace that brings visit records, follow-ups, stock and reporting into one operating view.
Client-reported comparison of typical daily administration before and after launch. Specific to this workflow.
See the real buildWhat we deliver
One useful workflow. Yours to keep.
Pick one process that keeps stalling, losing details or coming back to you. For selected businesses, we build the first agreed workflow without an implementation fee. We want to earn a longer-term working relationship through results; buying more is optional.
For example: a client brief becomes assigned work. AI prepares a plan from approved information, a manager reviews changes, and the team works from the current brief through to an approved handoff.
What we can measure together
- Time from request to accepted completion
- Repeated updates and owner interventions
- Work that stalls, fails or needs correction
- 01
One process, agreed from start to finish
Check fit and feasibility, then agree the people, tools, output and success checks. The free scope, running costs, delivery plan and correction process are written down before we start.
- 02
A system tested with your team
Build the workspace, connections and AI assistance the process needs. Review working demos, test exceptions and keep important decisions with your team.
- 03
A handover you can keep
Review the result with your team and provide the agreed access, operating rights, instructions and training. You can keep the delivered workflow without buying further development or support.
For an accepted free-workflow engagement
No implementation bill.
No obligation to continue.
No implementation bill
The implementation fee for the agreed first workflow stays zero, even if it succeeds or you decline further work. Extra work and external costs require your prior written agreement. No automatic retainer or surprise build invoice.
Keep the delivered workflow
Declining further work does not remove the agreed access, usage rights or handover for the delivered workflow. We identify what you need to run and maintain it. Third-party licences, running costs and ongoing support are agreed separately.
30-day defect cover
Report reproducible defects against the agreed scope within 30 days of accepted handover. We address covered defects without an implementation charge through the agreed correction process, including the remedy for unresolved material failure. Timely reports stay covered while that process is completed. New features and later external platform changes are separate.
From our first conversation to a working change
- 01
Define the smallest useful system
Choose the people, records and decisions for the first release. Agree what it must do and what can wait.
- 02
Build and review in working demos
Use real workflow examples to check the behaviour together. New ideas become explicit scope decisions, not hidden additions.
- 03
Test, adopt and operate
Your team checks the agreed acceptance cases. Prepare access, training and support, then improve the system from actual use.
Before we talk
The useful details.
Who qualifies for the free first workflow?
We look for a real recurring problem, a decision-maker and staff tester who can participate, feasible access to existing tools, and a useful small result that can be handed over. There should be a plausible need and budget for further work, but no purchase is required. We confirm eligibility personally before accepting a free build. One accepted offer per organisation or business group.
What is free, and what might still cost money?
The agreed first workflow has no implementation fee, even if it succeeds. It does not include a full-company audit, a complete Company OS or a whole product subscription. We disclose hosting, software, AI usage and other necessary running costs before you agree. Additional development and ongoing support need separate written agreement.
Do we have to start with the free workflow?
No. You can commission a paid project or ongoing FDE engagement directly. Clinic and restaurant subscriptions have their own packages. For organisations with procurement or ICT approval requirements, any evaluation must follow the approved route; a free build does not guarantee a later contract.
What if the workflow does not meet the agreed checks?
We follow the correction process agreed before the build. If a material failure remains unresolved, we close without an implementation charge, restore the previous process where needed and hand over usable work with its limitations recorded. We agree safe testing and exit arrangements before changing your live workflow. New requirements are separate scope, and existing client agreements keep their original commitments.
Can you turn something we built in Claude into a system for the team?
Yes, we can assess the prototype and what it needs for shared use. That includes durable storage, accounts, permissions, data validation, integrations and recovery. Some parts may be reusable; others may need to be rebuilt.
Who owns the system and the data?
We set out source code rights, account ownership, data access, export options and handover in the proposal. Third-party services have their own terms. These arrangements should be clear before building begins.
What can an AI agent do inside our system?
An agent can read a support case, find the relevant approved procedure and prepare a response or follow-up task for review. We give it a defined role, approved tools, limited permissions and an action record. Your team approves consequential actions. See Cornerstone, our own company system.
What happens after launch?
We agree the operating model before launch: who hosts it, monitors failures, handles support and approves changes. Ongoing support can be scoped separately from the initial build. Future features are prioritised from real use.
What do we agree before starting?
Private means access is designed around your team and workflow. Data location, AI providers, retention, source ownership and exit arrangements must be agreed for the actual build. Sensitive decisions stay with authorised people.
Your workflow is the starting point
Show us the work your current tools cannot hold together.
Bring one recurring problem, the tools involved and who needs to use the result. We’ll check whether it fits the free first workflow or a separately scoped project. A brief starts the conversation; it does not commit you to paid work.
Find my starting point