This scoping engagement covers the RFP Generation epic of the ICHRA Benefits Administration Platform - the tool used to model and present an ICHRA cost comparison for an employer, before any commitment to move forward with Gente.
This is a Time & Materials engagement, which means Gente can stop at any point without obligation to continue. The objective is to produce artifacts - user stories and a report - that Gente can hand to any developer and say "build this." Without that groundwork, whoever eventually builds it - Hite Labs or someone else - would have to scope and define it from scratch, working from their own assumptions about what it should be.
There's real variance in what this tool could look like. Rather than locking into one direction, this engagement produces a few viable options, grounded in actual discovery rather than guesswork, while still giving a concrete development starting point - whether the eventual build is AI-assisted, traditional development, or some hybrid of the two.
This also starts to surface what time, resourcing, and roles the broader ICHRA platform effort will need - not just what it costs to build the RFP Generation tool, but what it costs to maintain it. The data landscape this tool depends on - carrier APIs, plan data, regulatory rules - will keep changing, so a one-time build isn't the end state. This is a way to gather real, factual information about what's possible against what Gente actually wants and needs, not a claim that the result is future-proof.
Business Discovery and Data Discovery run concurrently rather than back to back, and Business Discovery and User Stories work as a loop - early stories surface gaps that send the work back to another round of discovery, repeating until the stories have real depth and breadth. Only once that loop settles does Prototype begin, and Prototype itself is optional rather than assumed.
The Prototype shows what a user would see - the intake fields, the plan options, the report output - using representative data, without running the underlying calculations live. It draws on the real data shape and real business rules surfaced in the User Stories and Report to put together a mock run of what's possible, grounded in the actual facts known at that point, at a fraction of the cost of a full build.
Goal: Produce a complete, portable foundation for the Proposal Generation tool - work that can be handed to anyone who executes it, not just used internally - and determine whether a working prototype is worth building on top of it.
Business Discovery: Working backwards from proposals that have already been built to capture what was included and why, and where business rules like affordability modeling and controlled-group aggregation actually originate. The takeaway: a documented, reusable source of truth for the domain logic, not knowledge that lives only in one or two people's heads.
Data Discovery: Reviewing what's publicly documented across the carrier and plan data vendors (Ideon, HealthSherpa, and a third source) to understand API shape, coverage, and where sources might overlap or conflict. The takeaway: a realistic read on what data is actually available to build against, and an early flag on the reconciliation question before it becomes a separate epic.
User Stories: A user story is more than a one-line request. It pairs a concrete example of something a person can do in the tool with the acceptance criteria - from both a business and a technical perspective - needed to actually execute that unit of development work. The takeaway: a shared, unambiguous spec of what "done" means for each piece of functionality, usable by anyone who might build it, not just Hite Labs.
Report: Because this tool doesn't exist yet, there's more than one reasonable way to build toward the same vision. The report lays out a few different plans - each a different combination or sequencing of the user stories - and links each plan back to exactly which stories it requires. The takeaway: instead of a single estimate, Adam gets a few real options for how much of the vision to build now versus later, each with its own cost and its own defined scope.
Prototype (Opt-in): A clickable, scripted demo of the intake, plan-data, and report-generation sub-processes with toggle logic between them, using mocked data. The takeaway: a way to pressure-test the chosen plan before committing real build hours to it - not a finished product, but real enough to expose what won't work.
$1,500.00 - $3,200.00