Who can do what?
Throughout the project, MAES Core defines tasks, tools and permissions for people and AI agents.
THE MAES SOFTWARE SUITE
Whether you are creating an app, adding a feature or running a campaign, MAES software helps you make decisions, builds the solution and verifies the outcome.
Software that works with your teams, AI agents or both.
At every stage, decisions, work, tests and their evidence are accounted for.
In development · Talk to us about your needs.
HOW A TECHNICAL PROJECT PROGRESSES
For an app, website or feature, the journey starts with a need and a working beta, followed by a plan for building a robust, verified solution.
Who is it for? What need will it meet? Which features matter? MAES Decide compares approaches and helps choose a direction.
At this stageA defined project and reasoned choices.
MAES Factory builds the beta: screens, features and user journeys. This is the place to try, refine and explore with more flexibility than in MAES Build.
At this stageA working beta to try out and refine.
MAES Architecture assesses the whole project: risks, data and dependencies between features. It defines work packages, their sequence and the checks to carry out in MAES Build.
At this stageA plan: what to build, in which order and with which checks.
MAES Build implements each work package following the authorised plan. It builds, tests, fixes and gathers evidence for approval of the result and its release.
At this stageVerified work, supporting evidence and a cycle summary.
MAES Architecture breaks the project into work packages called “slices”. Each one sets out what to build, what needs to work first and which tests to run.
For example, a language-learning app needs to save exercise results before it can calculate a user’s progress. MAES Build follows this plan to build and check each part.
From the first trial to final approval, the whole journey is accounted for, including discarded approaches, failed tests and fixes.
Throughout the project, MAES Core defines tasks, tools and permissions for people and AI agents.
Kallistos Pilot is designed to bring progress, outcomes and their sources together, helping explain blockers and inform the next steps.
MAES Studio is designed to create content and prepare distribution. Audience research and results guide the work before, during and after a campaign.
ACCOUNTING FOR THE WORK
Accounting for work means recording decisions, actions and outcomes as entries, with supporting evidence. Planned, completed, verified and pending work remain distinguishable.
The business can trace who did what, when, where, how and why, whether the contributor was a person or an AI agent.
A SUMMARY FOR EACH CYCLE
The summary connects the original goal with the work, tests, approvals and any outstanding issues. It explains the outcome and what still needs follow-up.
If a problem appears, you can trace versions and evidence to investigate its cause. What you learn informs better decisions and improves the next delivery.
Explore MAES Build in detailSEE AN EXAMPLE
See how a team and AI agents create a language-learning app: choose its features, build a working beta, plan the architecture, then build and test the final version. Every stage leaves a record.
4 min · English narration and captions.
Fictional scenario · Illustrative footage, diagrams and demonstration interfaces.
Playback could not start. Try again using the video controls.
On your phone, use full screen and turn your device sideways to read the diagrams more easily.
Use the full-screen button in the video controls.
OUR INTERNAL STANDARDS
We created KSS to set out how decisions, delivery and checks should work: who may act, what needs approval and which evidence to keep.
MAES software is designed to apply this internal framework. It is not an external certification.
Make clear what is established and what still needs checking.
Give each person or agent a defined task, permissions and limits.
Keep the options considered, the reasoning and the success criteria.
Compare the result with the authorised work and retain the evidence.
Document changes and lessons while preserving earlier versions.
START WITH YOUR NEED
Tell us about your project or organisation. We discuss your needs, then agree with you on the scope of a review and the software adaptations to explore.
Discuss my project Software in development · We discuss available features and adaptations with you