Discuss a project For operations teams in Australia, the US and the Philippines
We build document workflows, operational assistants and data products around a job your team does every week. Each system is tested on your own examples, and anything that needs approval waits for a person.
Read incoming documents, pull out the details your team needs and flag anything missing or conflicting for review.
Example Claims intake. Each submission is checked against the required documents. Complete files are queued for approval, and incomplete ones go to a reviewer with the missing items listed.
Answer questions from your own policies and records, draft briefs and follow-ups, and show the source behind each answer. Anything that needs approval waits for your team.
Example Lead follow-up. For each new inquiry, the assistant gathers what your team already knows, drafts a first reply and queues it for a person to review and send.
Turn data you are allowed to use into reports, dashboards or APIs built around a specific decision.
Example Operations reporting. Exported records become a weekly view of backlog, exceptions and turnaround by team, with a note on what the data does not cover.
These examples show the kind of system we build. They are not client case studies.
Explore what we build.In this example, the system organizes details from documents the team has permission to use. A required detail is missing, so it sends the record to a reviewer.
Documents the team has permission to use
A record is prepared for review
A reviewer must complete or reject the record.
An approved record can move to the next step.
On a project, we agree who may use the documents, who reviews flagged records and how mistakes get corrected. Access, approvals and testing
We plan the first phase to end with a working system tested on your own examples, so you can judge it on real cases before deciding on wider use.
You can hire us to build a system for your own team.
If you have data, industry knowledge or a way to reach customers and want to build a product or venture around it, a partnership may fit better. Tell us what you could contribute and the customer problem you want to solve.
SageDynamics is a Singapore company, and we work from Makati in Metro Manila.
Our working day overlaps with Australia's, so calls and reviews happen in Australian business hours.
With US teams we work mostly in writing, with calls at the start or end of your day.
Bernd is a software engineer and data scientist who has built technology products across three continents over two decades. Outside SageDynamics, he serves as CTO across several VS12 ventures, including Agent Image, a real estate web platform that has built more than 27,000 agent websites in North America. He was previously Chief Data Scientist at mClinica, now SwipeRx.
Bernd writes about AI, work and the Philippine services industry.
Read the essaysA hackathon series for engineers in the Philippines, founded by Bernd.
HackManila.comCompany updates and notes on building AI systems and data products.
Read Insights.Describe how it works today and where it gets stuck. A short, non-confidential description is enough to start.
Exploring a data product or venture? Start with partnerships.