About · Apogee · powered by ESAP AI

We're the people who got tired of waiting.

Nobody — and we mean nobody — was building this for the people running things. Every AI startup chose the easy half: customer support, sales tooling, developer copilots. The hard half — the systems your business actually runs on — sat untouched, because internal systems are deep, weird, and break in ways generic agents don't understand. So we built one that does.

The manifesto · short version

AI for customer support? Solved twelve times. AI for sales? Drowning in copilots. AI for developers? Practically a religion.

But the branch managers, the inventory leads, the kitchen supervisors, the warehouse foremen, the dispatchers — they're still doing what they did fifteen years ago. Six tabs, three approvals, copy-paste between systems that should be talking. They learn another dashboard every time the company upgrades anything. And every time the company hires someone new, the same training cycle starts over — because the AI tools that flooded the market in the last three years assume the user already knows what they're doing.

Apogee is for them. Not for the people who decide. For the people who run things — and for the new hires who are one stuck-form away from quitting. The category we're claiming is operations AI, and it's the unsexy one. The one that doesn't fit in a chat window. The one that has to live inside the POS, the ERP, the HR system. The one that needs to be audited, bounded, reversible — because operations is where the real money moves. And the one that has to take over when the operator is new, tired, or stuck in traffic for an hour, because performance is what should be graded, not the chair they were supposed to sit in.

Principles · 4 / 4

What we believe, in four lines.

01

Operator-honest.

We're blunt about how broken operational software is. We're sympathetic to the people stuck using it. We're quietly confident about the fix. Not corporate. Not aspirational. Specific.

02

Bounded by design.

Every action APO takes is a proposal. Tier-gated, blast-radius scored, fully reversible. If an autonomous system can't be undone, it shouldn't be autonomous yet.

03

Grounded in your data.

APO never makes up a number it can't trace back to a row. Every claim cites its source. Operators get the receipts; auditors get the trail.

04

Performance over presence.

We measure what gets done, not who showed up on time. The observatory grades work, not chairs.

Team · operator-engineers

The people who built this.

Six operators and engineers behind Apogee — the people who got tired of waiting for someone else to build the fix, and built it.

Syed Imam
Syed Imam
Founder & Architect
Usman Nazir
Usman Nazir
Head of AI
Mohamed Mostafa
Mohamed Mostafa
Frontend Engineer · AI Platform
Abdur Rahim
Abdur Rahim
AI Engineer
Atik Rahman
Atik Rahman
AI Engineer
Golam Kibriya
Golam Kibriya
AI Engineer
Timeline · so far

How we got here.

2020
A construction consulting firm is drowning in Excel and paper. We build a custom in-house ERP that bends to their exact workflow instead of forcing them to change. Eight months later, 80% of the paperwork is gone — and nobody needed training to use it.
2021
Migration and automation: attendance, payroll deductions, expense tracking — automations nobody was shipping yet. The owner spins up a software company around what we'd built.
2022
AI agents start to look real. We see past automation to something bigger — an agent that operates the system for the end-user, not just around them. ESAP AI begins.
2023 – 2025
ESAP AI takes shape: architecture and orchestration over raw LLMs. A framework that can run any business logic dynamically — full CRUD, across industries and workflows.
2026 · now
Apogee — the operations framework for AI agents. Agents that live inside the ERP and run it, so people just provide the data and review the work. First pilots underway.

Want to be on the next line of this timeline?

We're running a small number of pilots a quarter. Bring a lifecycle, bring an honest problem. We'll bring APO.