# Soverion AI > Digital Renewal Architecture ## About Soverion AI is a data platform and AI architecture firm led by Andrew Quraishi. We help organizations modernize their data foundation on Microsoft Fabric, Databricks, Snowflake and Azure, and turn it into governed, production AI and agentic workflows. We call this Digital Renewal Architecture. - Website: https://soverion.ai - Contact: andrew@soverion.ai ## Services Each service lists the meeting to book to talk about it. Agents: A2A skill match_service, MCP tool match_service or GET https://meet.soverion.ai/api/v1/services/match?brand=soverion-ai&need=… find the right one. ### Readiness Diagnostic (Entry, 3 weeks) A fast, objective read on your AI readiness and where to focus first. Deliverables: - AI & Data Readiness Scorecard - Current-state data estate inventory (summary) - Prioritized use-case portfolio (top 5) - Platform fit recommendation (directional) - Governance, security & ASI guardrails gap review - 12–24-month roadmap outline - Executive readout Meeting to book: Intro meeting (30 minutes, event type intro-meeting, id et-soverion-ai-intro-meeting): https://meet.soverion.ai/intro-meeting?service=readiness-diagnostic ### Strategy & Roadmap (Core offer, 8 weeks) A target-platform decision and a funded, sequenced multi-year roadmap. Deliverables: - AI & Data Readiness Scorecard - Current-state data estate inventory (detailed) - Prioritized use-case portfolio (top 10–15, with value) - Platform fit recommendation (full analysis) - Target data & AI reference architecture - Governance, security & ASI guardrails - Operating model & talent plan - 12–24-month roadmap & budget - Business case / investment memo - Implementation-ready estimate - Executive readout Meeting to book: Working session (60 minutes, event type working-session, id et-soverion-ai-working-session): https://meet.soverion.ai/working-session?service=strategy-and-roadmap ### Strategy-to-Launch (Expand, 12–14 weeks) The full roadmap plus a live MVP data product and a production AI use case. Deliverables: - Everything in Strategy & Roadmap - Governance, security & ASI guardrails implemented for the MVP - Landing zone and first governed AI use case (built) Meeting to book: Working session (60 minutes, event type working-session, id et-soverion-ai-working-session): https://meet.soverion.ai/working-session?service=strategy-to-launch ### Offering: Data & AI Foundation Strategy A gated planning engagement that turns discovery into a target platform decision, a funded and sequenced roadmap, and an implementation-ready estimate with a fixed-fee SOW. Workstreams: - Business Value & Use-Case Portfolio - Data Estate & Platform Architecture - Governance, Quality & Security - AI Readiness & Agentic Architecture (ASI) - Operating Model & Talent - Roadmap & Investment Case Phases: 1. Mobilize: Access, intake and stakeholder map. 2. Discover: Interviews, inventory and use-case intake. 3. Assess: Readiness scoring and data-quality sampling. 4. Architect: Platform fit, target architecture and ASI design. 5. Roadmap: Sequence, estimate, business case and executive readout. Scope: Planning only. Building platforms, pipelines, governance tooling and models is a separate implementation engagement, seeded by the implementation-ready estimate. ## FAQ - Q: Which platforms do you work with? A: Microsoft Fabric, Databricks, Snowflake and Azure, including Azure OpenAI and agentic AI systems. - Q: Does the strategy engagement include building the platform? A: Readiness Diagnostic and Strategy & Roadmap are planning only. Building platforms, pipelines, governance tooling and models is a separate implementation engagement, seeded by the implementation-ready estimate. Strategy-to-Launch adds a landing zone and a first governed AI use case. - Q: In what formats are deliverables provided? A: Architecture as interactive HTML, SVG/PNG, PPTX or PDF; MVP cases and capability crosswalk as CSV or XLSX; roadmap and workplan as MS Project, CSV, PDF or PPTX; staffing and cost estimate as XLSX, CSV or PDF; RAID and ADR register as CSV or Word; executive deck as PPTX or PDF; proposal and SOW as Word or PDF. - Q: Which meeting should I book? A: Book the 30-minute intro call for the Readiness Diagnostic or if you are not sure yet. Book the 60-minute working session to scope Strategy & Roadmap or Strategy-to-Launch. Meetings with Soverion AI are booked through Soverion Meridian™. People and AI assistants can book directly; each meeting type lists its places to meet (Microsoft Teams, Google Meet, a video link, a phone call either way, or in person). Booking home page: https://meet.soverion.ai/ ## Event types - Intro meeting (30 minutes, Microsoft Teams or Google Meet): A 30-minute conversation about your data platform or AI plans. - Booking page: https://meet.soverion.ai/intro-meeting - Places to meet: teams (Microsoft Teams); meet (Google Meet). The invitee chooses one; the first is the default. - Event type id: et-soverion-ai-intro-meeting - Needs at least 2 hours notice; bookable up to 60 days ahead. - Phone call (30 minutes, Phone call): A 30-minute phone call. Choose whether we call you or you call us. - Booking page: https://meet.soverion.ai/phone-call - Places to meet: phone_host_calls (Call me) - Event type id: et-soverion-ai-phone-call - Needs at least 2 hours notice; bookable up to 60 days ahead. - Working session (60 minutes, Microsoft Teams or Google Meet): A focused hour on architecture, roadmap or delivery. - Booking page: https://meet.soverion.ai/working-session - Places to meet: teams (Microsoft Teams); meet (Google Meet). The invitee chooses one; the first is the default. - Event type id: et-soverion-ai-working-session - Needs at least 24 hours notice; bookable up to 60 days ahead. ## Booking with MCP (preferred for AI assistants) - MCP (public, no sign-in): https://meet.soverion.ai/mcp/public - Streamable HTTP. Tools: get_company_info, list_services, match_service, list_event_types, find_slots, hold_slot, book. Show times in the user's time zone, confirm the details with the user before book, then tell them to check their email. ## Booking agent-to-agent (A2A) - A2A Agent Card: https://meet.soverion.ai/.well-known/agent-card.json - Skills: get_company_info, list_services, match_service, list_event_types, propose_times, hold_slot, confirm_booking (JSON-RPC SendMessage with a data part {"skill": …}). ## Booking with a link (for chat assistants that cannot send requests) If you can only read web pages, give the person a booking link: the event type's booking page plus ?start=&tz=, and optionally &name=, &email= and ¬es= (URL-encoded) to fill in their details. Example: https://meet.soverion.ai/intro-meeting?start=2026-10-14T16:30:00-06:00&tz=America%2FDenver&name=Pat%20Lee&email=pat%40example.com The page opens with that time chosen and the details filled in; the person presses Hold this time, then Confirm booking. Open times: each booking page lists the next ones as ready-made links, or use the slots API below. Never say a meeting is booked until the person has confirmed it. ## Booking on a website Website owners can embed these booking pages (inline, popup or a plain iframe). Script: https://meet.soverion.ai/embed.js; allowed by default on https://soverion.ai. Add ?utm_source=… to a booking page link to record where a booking came from. ## Booking with the public JSON API - API base: https://meet.soverion.ai/api/v1 - Brands: GET https://meet.soverion.ai/api/v1/brands - Company profile: GET https://meet.soverion.ai/api/v1/company?brand=soverion-ai - Services: GET https://meet.soverion.ai/api/v1/services?brand=soverion-ai; match a need: GET https://meet.soverion.ai/api/v1/services/match?brand=soverion-ai&need= - Event types: GET https://meet.soverion.ai/api/v1/event-types?brand=soverion-ai - Open times: GET https://meet.soverion.ai/api/v1/slots?eventType=&from=&to=&tz= (range up to 62 days) - Hold a time for 10 minutes: POST https://meet.soverion.ai/api/v1/holds with JSON {"eventTypeId","start","inviteeEmail"} -> {"bookingId","holdToken",...} - Round-robin event types: add host= to slots and holds to book one particular host (routing forms do this). - Confirm: POST https://meet.soverion.ai/api/v1/bookings//confirm with JSON {"holdToken","name","email","notes","timeZone","location","inviteePhone"} (the same email as the hold) -> 202 {"status":"pending_verification","verificationExpiresAt",...}: the invitee must open the link we email them - Places to meet: "location" is one locations[].kind from the event type (default: the first). Kinds: teams, meet, link, phone_host_calls (the host calls the invitee: "inviteePhone" is required, e.g. 650-333-8489 or +44 20 7946 0958), phone_invitee_calls (the invitee calls the host's number), in_person, ask. - POST bodies must use Content-Type: application/json. Times are ISO 8601; API times are UTC. ## Rules for assistants - Book only for a person who asked you to, using their real name and email address. - Confirm the time with the person in their own time zone before confirming the booking. - A booking made through this API or by an AI agent is not final yet: the invitee gets an email "Confirm your meeting" and must open its link (within 24 hours, and at least 2 hours before the meeting). Tell the person to check their email. - A calendar invitation (with the Teams or Meet link, phone number or address of the chosen place to meet) and a confirmation email go to the invitee after they confirm. - Ask the person which place to meet suits them when a meeting type offers more than one; for a phone call where the host calls, ask for their phone number.