Org GPT

Embassy runs on systems of record: SharePoint for documents, HRMS for people, SAP for finance, plus payroll, travel and expense platforms. Each holds what an employee needs. None of them answer a question.

Org GPT sits alongside those systems and exposes them through a single conversation. An employee asks in plain language; the platform retrieves what they are entitled to see, calls the right business system, and completes the transaction. It runs on the web, on a Windows desktop client, on native iOS, as an installable PWA and inside Microsoft Teams, from one backend and one design system.

Reckonsys is engineering the platform end to end: architecture, build, hardening and release across all five surfaces.

The programme is structured so Embassy makes its second investment decision on working software rather than a slide. Two commercially independent phases, each sized and accepted on its own.

Delivery runs as dual-track agile: a discovery and design track one sprint ahead of build, and a build track shipping behind feature flags with a demo every two weeks. Trunk-based development, mandatory review, infrastructure as code for every environment, and an LLM eval pipeline that blocks merges on regression.

• Phase 1: MVP in users' hands
  The Windows and native iOS clients, the permission-aware SharePoint backbone, the RBAC governance module, the multi-provider switch, and the first slice of business agents: holiday calendar, travel expenses, multi-invoice reimbursements, payslips and SAP password reset. At the end of it, Org GPT is live, governed, and transacting against real Embassy systems.
• Phase 2: Depth and reach
  PWA and Microsoft Teams surfaces, multi-model response comparison, task management, long-context memory, agent routing depth, rich in-chat UI responses, curated golden databases, structured-database retrieval over an entity ontology, and the remaining leave and travel agents. Triggered only once Phase 1 is accepted.