Technical Business Analyst — Architecture Control & MarTech Automation (B2B SaaS, ongoing) We are an international B2B procurement SaaS platform (RFx / supplier management), active in the US, Brazil, Indonesia, and India. We are building a multi-channel communication platform on top of Twilio and OpenAI GPT-4o across three phases: • Phase 0 (in progress): transactional email via Twilio SendGrid • Phase 1: multi-channel notifications via Twilio Messages API (WhatsApp, SMS, Email) • Phase 2: AI-powered dialogs via Twilio Conversational Relay + GPT-4o (US pilot) Development is distributed across multiple independent contractors and teams. Each team operates within its own scope and does not have visibility into the full system. The analyst’s role is to ensure that every team’s output fits precisely into the global architecture — in technical language, at the code and spec level. What you will do: • Translate business automation patterns and marketing logic into unambiguous technical specifications with clear acceptance criteria • Maintain the master trigger map (50+ triggers across supplier, buyer, onboarding, engagement, risk, LTV categories) and translate each trigger into a technical task • Review and audit the output of external contractors — verify that implementations match the architectural spec before acceptance • Run as-is / to-be audits at contractor onboarding: document current state, identify deviations, get written sign-off before work begins • Enforce cross-team architectural consistency: different contractors must produce components that connect without friction, even when they don’t see each other’s work • Control that Zinit remains the system of record: delivery statuses, dialog transcripts, AI outputs, and communication context must return to Zinit — not remain in Twilio • Flag technical risks that would create vendor lock-in, data sovereignty issues, or investor due diligence problems • Produce clear written documentation at every stage — specs, audit reports, architectural decisions Tech context (no coding required, but must understand at spec level): • Twilio ecosystem: SendGrid, Messages API, Conversations API, Conversational Relay, Voice API • OpenAI GPT-4o integration via Twilio Relay • Event-driven architecture: event contracts, outbox pattern, idempotency, webhook callbacks • Data ownership boundaries: what must stay in Zinit vs what can live in Twilio • Django / PostgreSQL data models at reading and review level • Metabase for communication analytics Ideal background: • 3+ years as BA, Technical BA, or Product Owner in SaaS or MarTech • Experience working with multiple independent contractors or teams on a single product • Has worked on a project involving Twilio or comparable CPaaS (MessageBird, Vonage) • Can read a technical spec and identify what’s missing, ambiguous, or architecturally inconsistent— without writing the code yourself • Understands the difference between a transactional notification and an AI dialog — and what that means for data storage and system design What we provide: • Phase 0–2 specs, trigger map, architecture decisions, Event Contract schema, data ownership principles • Access to ongoing project context across all contractor workstreams Engagement: part-time, ongoing, fully remote.