Engagement files
What we have built.
1AYM publishes five engagement files: a governed finance data connector, an IELTS speaking assessment built as a measuring instrument, AI, data and automation enablement across a global agency, identity provisioning for 1,000+ users across 600+ groups, and a clinical-research platform taken from stalled build to launch. Each states what was built, what it measured, and what the client kept.
Written at a public-safe level: capability, constraints and numbers. Clients are not named; internal project names and proprietary business logic are held back.
2 of these files describe separate workstreams within the same client engagement, and say so on the page. It is one relationship that kept widening, not several.
Self-serve finance answers, without breaking permissions
Client withheld
A question about client or financial performance used to take around two hours to come back from the finance team. It is now answered in the meeting where it is asked, and nobody gained access they did not already have: the connector carries each person's existing Looker entitlements, so people see exactly what they were already entitled to see.
An IELTS speaking assessment built as a measuring instrument
A government-accredited EdTech in the Middle East
We hold end-to-end technical ownership of a government-accredited EdTech's live production estate, and its IELTS speaking assessment is the centre of it. Most AI speaking scorers are one model call wrapped in a product; this one is a measuring instrument.
AI, data and automation enablement across a global agency
A PE-backed marketing agency
Sessions on this agency's AI platform now cost 60% less on average than they did before we re-architected its skills estate. An earlier change, a per-user API call replaced with one ten-minute sync, carries a forecast saving of £2–4M a year, modelled on token consumption and reviewed by the client's finance team.
Identity provisioning for 1,000+ users across 600+ groups
A PE-backed marketing agency
When somebody leaves, their access to Notion and Claude ends with their HR record rather than when a colleague remembers. We built the provisioning system that does it from scratch, because the client's IT team was over capacity and off-the-shelf group tooling did not fit a model where one person belongs to many groups: it covers more than 1,000 users across over 600 groups and has run for seven months.
A regulated product that was not going to ship, shipped.
A clinical-research software start-up
A clinical-research software start-up had a part-built platform, no engineering environment its own team could ship from, and a launch that was not going to happen on the path it was on. We worked with the founders: first a development environment, with repositories, environments, continuous integration, review gates and a release discipline, then completion of the platform, then delivery to launch alongside their team.
Last reviewed · 1AYM