ALIGN
One free 30-minute Fit Call. Then paid Foundation — a fixed fee scoped by problem breadth — process capture, an opportunity map, and a costed roadmap.
AI Transformation & Systems · Mauritius
The connected layer your business actually runs on — workflows, records, portals and a governed assistant. Built one release at a time, with the scope and the price agreed before anyone starts.
01 · Approach
Aya draws a boundary around one workflow, names who owns it, and states what is inside and outside the first release. Widening it is a separate decision with its own cost — and you make it.
One person on your side owns each release, and one person at Aya builds it — the same person who scoped it, through to production. No handover to a team you have never met.
Advisory, releases, reusable modules and live service are one apparatus at different magnifications — not four disconnected purchases.
Scope is a bracket that closes. The unclaimed remainder always stays visible — a plan that fills to 100% of its own width tells you nothing about what was left out.
One instruction overrides everything else. If a rule would force Aya to imply evidence, ownership, scale or approval that does not exist, the rule loses. Nothing outranks telling the truth about what exists.
02 · The client journey
One free 30-minute Fit Call. Then paid Foundation — a fixed fee scoped by problem breadth — process capture, an opportunity map, and a costed roadmap.
A defined website or operational product release. Every release runs on a Release Brief: outcome, included scope, acceptance, exclusions, dependencies, change treatment.
Reserved monthly capacity delivering agreed releases against a rolling 90-day roadmap. Capacity funds the current agreed release — not the entire backlog, and not unlimited vision.
Hosted Licence & Care, agreed before go-live, beginning after an included 30-day stabilisation period. Variable AI, video and messaging usage stays client-owned and transparent.
03 · Platform
Aya maintains a catalogue of reusable capability drawn from working software, and grades the evidence before it sells the label. Reuse is disclosed as reuse — Aya does not pretend to rebuild existing software, and does not sell a label as a product.
Branded modular operating workspace — navigation, module registry, responsive base.
▥ adapt · evidence-gradedControlled tenant and role access — sign-in, invitations, tenant boundaries.
▥ adapt · evidence-gradedPermission-aware assistance with bounded retrieval, review gates and explicit uncertainty.
▥ adapt · evidence-gradedShared staff communication in operational context — channels, messaging, attachments.
▥ adapt · evidence-gradedAuthenticated self-service and communication — profile, inbox, documents, actions.
▥ adapt · evidence-gradedCaptured website enquiries become traceable workspace records, not lost emails.
▥ adapt · evidence-gradedStructured operational coordination — assignment, status, priorities, selected workflows.
▥ adapt · evidence-gradedVisible lead ownership and follow-up — deliberately light, honestly labelled.
▥ adapt · evidence-gradedDecision visibility across activated workflows — agreed KPIs, honest data freshness.
▥ adapt| id | capability | family | class |
|---|
class legend — adapt: working substrate, client adaptation is material · candidate: working source, not yet deep-audited · pattern: accelerates custom work, not a product · net-new: scoped and quoted as bespoke work. Activation pricing is published per capability only after it passes the readiness gate; adaptation is quoted with explicit assumptions.
Advisory, Foundation, and Transformation Capacity — priced below. The catalogue is not a shelf you order from; it is what delivery draws from. Where a capability already exists as working code, your release starts from it. Where it does not, it is quoted as new work — and the catalogue says which is which. A capability earns its own activation price only after it passes the readiness gate. None has.
evidence grades as at 25 July 2026 · a label is identity, not readiness · certification requires end-to-end, persistence, permission, security and release evidence
04 · Provenance
Aya's reusable modules are not slideware. They are drawn from FridayOS — the operating system the founder built for his own hospitality company in Mauritius, where it runs day-to-day operations: staff collaboration, guest and owner portals, task workflows, lead handling, and a governed AI assistant.
That is the provenance claim, stated exactly: working software, in daily internal production, at one real operation the founder owns. It is not a claim that any module is certified, portable, or proven at your scale — that evidence is built per release, and priced only when it exists.
unit evidence at the audited source baseline · integration, load and per-client acceptance are release-scoped work, and are not claimed here
Test counts, audit grades, scope fractions, prices, dates. Everything on this page traces to a measured record.
Client savings, revenue uplift, conversion gains. Those get published per engagement, with the measurement method beside them, once they are measured. A results section earned this way is worth more than one written this morning.
05 · Selected work
Design states are labelled as design states. Live systems are labelled as live. Nothing here is a mockup pretending to be production.
One system, three faces: a public site where guests book direct, an owner portal onto the same records, and the operating system behind both — staff collaboration, task and workflow coordination, lead handling, finance and a governed AI assistant. It carries the business day to day, and it is where most of Aya's catalogued capability comes from.
A proposed operating system for an education provider: a director's daily briefing with human approval gates, an admissions pipeline, student and educator surfaces, and a public site with a governed Ask assistant. Every AI action shown is drafted for a person to approve — nothing is issued automatically.
Aya Corp has been building software since 2018. These shipped before the AI practice existed, and they are the reason the delivery discipline is not new.
Trading app · 4 weeks
Mobile development · 8 weeks
Analytics platform · 6 weeks
Marketing site · 3 weeks
delivered before Aya Corp's AI practice · timeframes and scope as recorded at delivery
An events operator's portal, currently being scoped. There is no design to show and no system to demonstrate. It appears here for the same reason the catalogue shows zero certified capabilities: the honest state of the work is the work.
06 · Engagement
You pay for each distinct thing once: advisory by the hour, Foundation discovery, switching on a capability that already exists, monthly build capacity, and running the live system. Variable AI, video and messaging usage stays client-owned. Nothing is charged twice.
Founder-led executive advisory on AI transformation — direction, sequencing, and honest feasibility before money is spent on software.
Paid discovery by problem breadth — one contained function, roughly three priority workflows, or multi-function work. A fixed fee, not an hourly meter: the hours below are what the work takes, not what you are billed for. Onsite observation, document review and interviews are Foundation work, not free consulting.
Reserved monthly capacity delivering agreed releases. Three-month initial term, then rolling. Plans name protected capacity — not vague speed, and not a promised percentage of a roadmap.
The live-service layer — hosting, monitoring, support and continuity. Agreed before go-live; recurring Care begins after the included 30-day stabilisation period.
all prices exclude VAT · catalogue activation prices are published only after a capability passes the readiness gate — none has
07 · Principles
No illusion of choice, fake scarcity, or countdown theatre.
No unlimited “full vision” promised for one retainer.
No false Zoom, Teams or Slack parity claims.
No “production-ready” claim based on a prototype or a polished UI.
No hidden pricing, silent scope inflation, or continuity conditions in fine print.
No invented clients, testimonials, awards or metrics.
No number in Aya’s voice that does not trace to something measured.
No charging twice for the same entitlement, task or deliverable.
Operator, not agency. Aya Corp is founder-led by Ishant Ayadassen — a builder-operator who has run companies across hospitality, software, marketing and finance, and built the operating software his own businesses run on. Advisory, transformation and product delivery come from the same person who has carried the operational consequences of both good and bad software decisions.
08 · Contact
One free Fit Call — 30 minutes, virtual. You bring one workflow that hurts. Aya states what a first bounded release would include, exclude, and cost to widen.