Services › Business analysis › Domain Build / Senior Technical BA
Business analysis engagement typeDomain Build / Senior Technical BA
One senior lead who learns your domain end to end (the business process, the systems, the data and the integrations) and turns it into a backlog your development team can build from and you can budget against.
You are the CEO of your world; this engagement type tells EliosTech where you want us. Vice-president–level ownership takes vice-president–level money, while a narrow individual or external-consultant focus can carry significant discounts. Contracts set the boundaries, EliosTech work is proprietary, and service continues while paid. How it works →
What this work is
Most projects do not stall because the developers cannot code. They stall because nobody owns the whole picture: who the subject-matter experts are, which system is the source of truth, what the API really returns, and how much work is actually left. That is the job of a Senior Technical BA, and it is the job EliosTech, Inc. takes on.
What EliosTech does in this engagement type
- Map the domain: people and SMEs, systems, data flows, integrations and the decisions each one owns.
- Document current-state and future-state processes in plain language the business signs off on.
- Write epics, features and stories with acceptance criteria, data rules and edge cases.
- Map APIs and data field by field: payloads, validations, error codes and who consumes what.
- Capture non-functional needs: security, performance, audit, reporting and support hand-off.
- Run backlog refinement, sizing and sprint demos with the development team.
- Keep a written estimate and budget tracker current every sprint.
What you get
- Domain map and system context diagram
- Story map and a refined, sized backlog
- API and data mapping documents
- Requirements traceability (story → test → defect)
- Estimate and budget tracker
- Demo-ready acceptance criteria every sprint
Good fit when…
- A program is starting and nobody owns the domain yet
- Developers keep asking the same questions the business never answered
- You need one person accountable for scope, estimates and the board
- You are replacing a departing lead and need continuity
Tools we bring to your development team
Over many engagements, EliosTech, Inc. has worked side by side with development teams on the tools they already run. We work inside your licenses, repositories and boards; we do not resell software or lock you into ours. The point is simple: a business analyst who speaks the team's tools turns requirements into working, tested software faster, with fewer surprises at demo time.
Microsoft .NET teams
We have spent years helping teams that build on Microsoft .NET: Web APIs, background services, integrations and the configuration around them. We read a solution well enough to know where a change lands (controller, service, data layer, config), write stories that match how the code is organized, and check each pull-request demo against its acceptance criteria. Your developers write the production code; we keep the requirements and the code honest to each other.
In this engagement type: stories written to the shape of the solution, so a .NET developer can pick one up without a meeting.
Postman
Shared Postman collections and environments for every endpoint in scope, so analysts, developers, testers and partners call the same requests with the same examples. Collections double as living documentation and can run in the team's pipeline (for example with Newman) as a quick API smoke test.
In this engagement type: we confirm what an endpoint actually returns before a story is written against it.
Redocly & OpenAPI
API contracts written and reviewed as OpenAPI, linted and published with Redocly so the reference docs stay in step with the spec in version control. Business rules, error codes and examples live next to the endpoint they describe, and partner teams read the same contract your developers build to.
In this engagement type: the contract is reviewed with the business before the developers build to it.
Jira, Confluence & Azure DevOps
The board is where the plan lives. We set it up to match the Epic kickoff (epics, features, stories, tasks), write acceptance criteria, refine and size the backlog, link stories to tests and defects, and keep the dashboards that show progress and budget every sprint. Same discipline in Azure DevOps Boards or similar tools.
In this engagement type: one board, one backlog, one owner. You see exactly what each sprint bought.
What our BAs do in Jira (and similar)
- Structure the board to match the Epic kickoff: epics → features → stories → tasks, so what you approved is exactly what the team works.
- Write stories developers can build and testers can prove: clear user stories with Given / When / Then acceptance criteria, data rules and examples.
- Refine and size the backlog with the team before each sprint, with agreed definitions of ready and done.
- Trace everything: link stories to API contracts, test cases, defects and the Confluence (or wiki) pages that explain the decisions.
- Report in the open: sprint dashboards, burn-down and a budget view, plus the written progress and change report you get with every demo.
- Triage and route defects so the right person fixes the right thing, and nothing new enters a running sprint without your written approval.
- Own the backlog on your behalf as the authorized party to the project: prioritized with you, never reshuffled without you.
Jira and Confluence, Azure DevOps Boards or the tracker you already use. We work in your instance and your workflow.
How it runs: Epic kickoff → Sprint 0 → Sprint 1
- 20-minute intro call → Epic kickoff: we walk the whole project (features, stories, tasks) and you decide whether the work and price are right for you.
- Sprint 0 needs the down payment first. About 2 weeks and up to about 30 days of investigation. It produces your Sprint 1 plan.
- You may decline Sprint 1. If you accept it, that scope is honored and demoed as completion. Then the next payment is due.
- After that, two-week sprints: steady two-week payments, a demo every sprint and a written progress and change report.
Rates and how this engagement type starts
| Engagement shape | Typical rate |
|---|---|
| Long-term remote engagement (roughly 1–2 years) | from ~$80/hr (typically $80–$140) |
| Onsite or heavier hybrid, Cook / Lake counties | ~$130/hr |
| Operating domain + crew (EliosTech runs analysts, developers, testers) | $140–$200/hr or an annual program |
| Short C2C surge, rescue or go-live push | ~$200/hr |
| Discovery = Sprint 0 (default start) | $8,000 down payment before Sprint 0 starts, confirmed in written terms |
| Sprint 1 and later sprints | Billed per two-week sprint from your accepted Sprint plan |
Senior bands, stated up front: domain ownership, not commodity staff augmentation. C2C through EliosTech, Inc. preferred. Longer terms and prepaid work move the rate down; short notice and onsite days move it up.
Configure this engagement type
- Configure the job below
- Estimate — a rough range, instantly
- Terms — read and accept
- Down payment — we invoice; kickoff goes on the calendar
Other business analysis engagement types
Payments modernization BA
Lockbox, cash application, payment APIs, processor onboarding and data maps, done terms-first with written estimates.
Read about this work →Business AnalysisFinance ERP / D365 BSA
Procure-to-pay, vendor, T&E and Power Automate workflows on Dynamics 365 Finance & Operations, through UAT and cutover.
Read about this work →Business AnalysisDiscovery / Sprint 0 leadership
Open the accounts, find the subject-matter experts, size what effort really remains, and leave you with a Sprint 1 plan and a budget tracker.
Read about this work →Business AnalysisQA, UAT, test plans & automation
Test plans, QA, UAT and automated API and regression testing. Hire EliosTech to take over the testing job as scoped sprint stories.
Read about this work →Rather talk it through?
A 20-minute scope call is free and tells you whether we are the right fit. Discovery (Sprint 0) is paid work that ends in a Sprint 1 plan you may accept or decline.