Business Architect

Entyre is building the fastest-growing elderly care company in the world. We exist to make it dramatically easier for families to get care when they need it most. We’re scaling quickly across the U.S., launching new markets and building durable operations. This is a company built for speed, execution, and real-world impact — and we’re looking for operators who want to build the systems that make that scale possible.

The Business Architect for Hub Expansion is one of the most operationally critical roles in scaling Entyre. This is not a “write requirements” job. You will own the engine that allows Entyre to launch new states and verticals quickly and consistently through Hub—our self-onboarding platform. You’ll take each new market from zero to live: defining what the business needs, translating it into clear product requirements, partnering with Engineering and Design to build the right solution, and driving launch readiness across the organization. You’ll also own enablement, training, and change management—making sure teams adopt what we ship and that each launch performs in the real world. This is a high-velocity, cross-functional operator role with direct impact on how fast we can grow. You’ll report to the Head of Product.

• Own the full lifecycle for onboarding new markets/states/verticals onto Hub: intake → discovery → requirements → build support → launch → stabilization.

• Develop a repeatable playbook for market launches so we can scale faster over time.

• Lead discovery with internal stakeholders (Marketing, Sales, Customer Success, Clinical, General Managers) to understand workflows, edge cases, and constraints.

• Define and document business requirements, service design blueprints, user journeys, operational flows, and acceptance criteria.

• Identify what should be standardized vs. configurable per market/vertical and drive alignment on those decisions.

• Partner closely with Engineering and Design to translate requirements into scalable product solutions.

• Facilitate tradeoff decisions (scope, sequencing, timeline, technical constraints) and keep teams aligned on outcomes.

• Ensure implementation meets business intent.

• Plan and run launch readiness: training materials, internal enablement, support documentation, rollout plans, and escalation paths.

• Coordinate with stakeholders to ensure operational readiness (process updates, staffing impacts, tooling changes).

• Own change management communications so impacted teams understand what’s changing, when, and how to use it.

• Track launch performance and adoption; identify gaps, issues, and optimization opportunities.

• Gather feedback and partner with Product/Engineering to prioritize improvements and reduce friction for future launches.

• New markets/verticals launch on time with clear scope, minimal surprises, and high stakeholder confidence.

• Hub adoption is strong: teams can onboard without heavy manual support or workarounds.

• Documentation is consistently high-quality (requirements, process flows, enablement materials).

• Launches get faster over time due to a repeatable playbook and better standardization.

• Fewer post-launch issues, reduced operational overhead, and measurable improvements in onboarding speed/quality.