A decade of experience, focused on one problem.
We started Hexaa in 2016 building web platforms and machine learning systems. In 2025 we narrowed the firm to document automation for operations teams, because that was the work that never stopped coming in. We kept the engineering depth we built over ten years. We just pointed it at the document work others call intelligent document processing.
What we believe
Three things that guide every engagement.
Documentation is part of the deliverable.
Every pipeline is handed back with runbooks an analyst who joins next year can follow. We learned this running ten years of engagements. Undocumented automations become tribal knowledge inside eighteen months.
Not every workflow is worth automating.
We have said no to more work since we narrowed than in the ten years before. It keeps us honest, and it keeps clients from spending six months on something a spreadsheet would have closed in a week.
The engineer on the scoping call leads the build.
No long hand-offs from sales to customer success to delivery. The person you brief at scoping is the person whose code runs in production. It makes misunderstandings close to impossible.
Where we are
Three hubs. One build cadence.
Austin
Texas · US Central
Client engagements, delivery leads, and US-facing engineering leadership. The hub that runs the scoping calls.
Brantford
Ontario · Canada Eastern
North American engineering coverage and operations. Timezone bridge between Austin and Lahore during build phases.
Lahore
Pakistan · PKT (UTC+5)
Engineering base since 2016. The largest concentration of the firm's engineering staff. Overlaps European mornings and North American evenings.
Continuous operation from Lahore since 2016. Austin and Brantford added as US and Canadian client engagements grew.
Working with Hexaa
From first call to handover.
A five-stage engagement. Every stage has a fixed output. Every stage ends in a go or no-go. You do not get locked into the next one until the current one delivers.
- 01
Scoping call
A free 30-minute call with the engineer who would lead the build. We learn the workflow. You learn whether this is worth building.
30 minutes
Free - 02
Paid discovery
Workflow map, exception register, integration surface, risk list, and a fixed-cost build estimate. Signed off before any build starts.
1-2 weeks
Fixed fee - 03
Build
Engineering lead and supporting engineers. Weekly demos against the workflow map. Code is yours from commit one.
4-6 weeks typical
Fixed scope - 04
Validate in production
Live documents, real exceptions, your team using it daily. We tune against real traffic until the exception rate is stable.
2-3 weeks
Included in build - 05
Handover
Runbooks, documentation, and internal training. Hexaa stays on a support retainer if you want it, or we exit cleanly.
1 week
Your choice of retainer
What you own
- All code, documentation, and runbooks, from commit one
- The deployment, infrastructure, and data
- The right to walk away at handover
- Direct contact with every engineer on the build
What we own
- The estimate, including any risks we did not surface at discovery
- The timeline. If we miss it, we fix it on our time
- Exception behaviour through validation, not just the happy path
- Handover quality: you should not need us the day after
