EliostechBook a fit call

I don't just analyze. I stand up the whole domain.

Most recruiters ask for a different slice of the same job: systems analysis, ERP workflows, product ownership, core implementations, data products. What I actually do is take a new domain — payments, lending, operations, analytics, whatever you need — and build the business under it so people can execute with clear boards, honest estimates, and real accountability.

What "domain build" means

When you hire me for a domain, you get the operating system of that workstream — not a pile of tickets.

  1. Domain map — how the business actually works: people, systems, data in/out, decisions, handoffs.
  2. Boards that match the work — Azure DevOps / Jira / similar, structured so status is visible without status meetings that waste everyone's time.
  3. Estimates you can run a business on — scoped work, prepayment options, and packages that scale from a solo engagement to a crew of subcontractors.
  4. Processes with accountability — who owns what, when it's done, how we know, and how we recover when it isn't.
  5. Integrations and systems analysis — ERP and core systems, APIs, data movement, source-to-target mapping, testing support — the bridge between business and IT.
  6. Handoff that sticks — documentation and rituals so the domain keeps running after the stand-up phase.

How a domain stand-up runs

Every engagement follows the same six steps. What changes is the domain — payments, banking, ERP, operations — not the discipline.

  1. 1

    Domain map

    We interview the people who do the work and the people who pay for it. Output: one diagram of actors, systems, data in and out, decisions and handoffs, plus a list of open questions and risks.

  2. 2

    Boards

    We set up or clean up your Azure DevOps or Jira: epics that match the domain map, stories with acceptance criteria, and a backlog sponsors can read without a walkthrough.

  3. 3

    Estimates

    A written estimate for the next phase: scope, assumptions, rate, and options for prepaid blocks or milestones. If the estimate moves, you see the delta and the reason.

  4. 4

    Accountability

    A named owner for every workstream, a weekly cadence (stand-ups, demos, release reviews or change board — whatever fits your org), and a simple rule for how slips get surfaced and recovered.

  5. 5

    Integrations

    APIs, data mapping, source-to-target, data contracts and the test scenarios that prove them. This is where business and engineering agree on what "done" means.

  6. 6

    Handoff

    Runbooks, process documentation and the rituals that keep the domain running after we step back — or a monthly program if you want us to stay on.

Skills people ask for — covered by one offer

Recruiters keep pinging for different titles. Same underlying capability:

  • Business Systems Analyst — process analysis, workflows, ERP integrations, requirements, testing, business↔IT bridge
  • Implementation / domain SME — configuration, data models, REST APIs, event-driven integration, conversion and reconciliation, go-live discipline
  • Product Owner (data & analytics) — Agile delivery, Azure DevOps, analytics products for finance/pricing/performance, cross-functional ownership

If the title on the requisition changes every week, the work does not: stand up the domain, make delivery accountable, keep the systems honest.

Recruiter & buyer packet

If you're filling a seat, here's how the asks we see most often map to John's background. Tailored resumes are available for each.

The requisition asks forWhere it comes from
Senior Technical BA (banking)Bridge between ops and engineering: specs, data contracts, data maps, UAT lead and executive Change Board (CheckAlt, Fiserv, CME). Light C#/.NET history supports the "technical" label. Not a solution-architect seat.
Business Systems Analyst (ERP / D365 / workflows)Dynamics 365 Finance & Operations on vendor onboarding, expense/T&E and labor workflows with Power Automate (C4 Technologies / KGPCo); Senior BSA at Best Buy (via C4)
Payments modernization / Payments BACheckAlt commercial payments — lockbox, eLockbox, IR, RDC, cash application; XML/JSON data maps; Recurly / partner payment wall at Chamberlain myQ
Finxact / core-banking SME (analyst scope)BSA IV on Finxact APIs and commercial banking client portals at Fiserv — account management, disputes, demographics, audit search. Analyst and requirements scope, not platform architect.
Product Owner (Data & Analytics)Product-owner delegate for partner integrations at Chamberlain myQ; SQL, Power BI and Splunk reporting; backlog ownership in Azure DevOps and Jira
Lead Technical BA (regulated finance)Lead Technical BA at CME Group (via Solving IT) — epics, UAT and data-migration checks with global stakeholders
Scrum Master / UAT LeadScrum Master and QA roles at Chamberlain myQ; UAT ownership across CheckAlt, Fiserv, CME and Best Buy engagements

Engagement basics for recruiters

  • Contracting: C2C through Eliostech Inc. preferred; W2 when the total package (benefits + rate) is strong.
  • Location: remote (U.S., Illinois-based), light hybrid in Cook and Lake counties, or downtown Chicago hybrid for banking Technical BA.
  • Rate guide: long remote contracts from ~$80/hr · onsite or heavier hybrid ~$130/hr · short C2C surge ~$200/hr.
  • Education: B.S. Computer Information Systems, Elmhurst University · MBA, University of the People.
  • Helpful to include: the JD, client or industry, remote/onsite days, contract length and rate range.

Engagement packages ($80–$200/hr)

Rate depends on duration, prepayment, estimate certainty, and how much of the delivery crew Eliostech runs.

Discovery & domain blueprint

Short engagement to map the domain, boards, and first 90-day plan. Fixed estimate preferred. Good when you need clarity before a long contract.

Domain stand-up (core)

I build the domain under your roof: boards, estimates, workflows, integration analysis, accountability cadence. Typical long-term contract band $80–$140/hr depending on length and prepay.

Operating domain + crew

Eliostech packages that pay subcontractors under the same estimate — analysts, developers, testers — while I own the domain and accountability. Higher band $140–$200/hr or monthly program pricing when we carry delivery risk and payroll for the scope.

Annual domain program ($200,000+/year scopes)

For scopes large enough to pay employees and subcontractors and still leave Eliostech a healthy operating margin. Structured like an Operating Partnership for a specific domain: one accountable lead, recurring estimates, prepaid blocks, and clear outcomes. Aimed at $200,000 a year or more of funded work for that domain.

Exact package and rate are set after a fit call and a written estimate — duration and prepayment move the number.

How we work together

  • C2C / W2 / subcontract structures as the client needs; Eliostech can sit as the contracting vehicle.
  • Written estimates before major spend; prepaid blocks when you want locked capacity.
  • Visible boards from day one so sponsors see progress without chasing status.
  • Fit call first — 20 minutes to see if the domain and the rate band make sense.

Based in the Chicago suburbs. Remote-ready for U.S. contracts. Domain stand-ups for payments, banking/core, ERP, and data products — and any new domain you need built for real.

Why these rates (competitive + owner overhead)

Senior BA / domain-lead contract rates commonly land in the $80–$200/hr band depending on specialization, duration, and risk. Eliostech prices in that market — not below it — because the engagement includes more than a staff-aug body:

  • Owner/president accountability: one person who owns the domain outcome, not a rotating bench.
  • Business overhead clients rarely see: entity costs, insurance, accounting, contracting, estimates, invoicing, and keeping subcontractors paid on time.
  • Delivery load beyond the hour: boards, process design, vendor coordination, written estimates, and accountability cadence.
  • When we run crew packages, rates fund paying analysts/devs/testers under the same estimate while Eliostech carries the operating risk.

Attractive means clear packages and visible accountability — not racing to the bottom.

Tell us the domain you need stood up

A sentence is enough: the domain, the systems, the timeline and the setup (C2C, remote, hybrid). We'll come back with fit, rate band and a next step.

Looking for a specific domain? Payments → · Finance ERP →