IDENTITY
title: "DEVXIO + STRUXIO MVP: 7-Day Blended Sprint Plan"
type: blueprint
subtype: execution_roadmap
purpose: "Compressed sprint plan that builds minimum viable DEVXIO factory (Days 1-3) then immediately pivots to ISO 19650 MVP revenue product (Days 4-7)."
GOVERNANCE & LEGAL
status: active
version: "1.0.0"
classification: "internal"
last_updated: "2026-03-14 17:45"
copyright: "© 2026 STRUXIO.ai"
legal: "Confidential & Proprietary. Do not distribute."
THE 7-DAY BLENDED SPRINT: FACTORY + PRODUCT
0. STRATEGIC CONTEXT
The Constraint: DEVXIO (the factory) exists to build STRUXIO (the product). Every hour spent perfecting the factory before revenue is a burn-rate liability. The factory must be "good enough to accelerate," not "perfect enough to admire."
The Team: Shai (Founder/Operator), Claude Opus 4.6 (Architect, Web UI), Claude Sonnet 4.6 (Coder, Roo Code).
The Target: By Day 7, have a functional ISO 19650 compliance service generating its first client pipeline.
Infrastructure Already In Place:
- Hetzner CPX32 running Docker Compose MVP (Next.js + FastAPI + LiteLLM + Neo4j)
- DEVXIO portal rendering at
http://89.167.96.154:3002
- Odoo.sh active at
struxio-platform-main-29652199.dev.odoo.com (linked to STRUXIO_App repo)
- 5 GitHub repos synced and committed
- All API keys (Anthropic, Google Vertex, etc.) provisioned
- Domain: struxio.ai on Porkbun
What We Are NOT Building This Week:
- K3s migration (Docker Compose works for <50 users)
- Qdrant / embedding pipeline (not needed for MVP)
- E2B microVMs (regular Docker is fine)
- DEVXIO Screens 3-6, 8-10 (only Screen 7: Approval Matrix)
- Helmfile, Argilla, LangFuse, adr-tools (all post-revenue)
- The Bootstrap Gate (aspirational, not critical path)
DAY 1: STABILIZE & CLEAN (DEVXIO)
Sprint Mode: ACTIVATED (per RULE_two_monitor_protocol.md Section 5)
Morning: Git Sync & Housekeeping
- TICKET_031: Sync all 5 repos on Hetzner (
git pull). Verify workspace graph. Purge .next/dev/cache/ from Git tracking. Confirm infrastructure_secrets.enc.yaml and struxio-vertex-service-account.json are in .gitignore.
Afternoon: Fix the 3 Sledgehammers
- TICKET_032: Fix Zustand
ThemeState interface (add tokens property), remove as any casts from ThemeInit.tsx and WorkspaceDashboard.tsx, fix WebSocket localhost bug, remove ignoreBuildErrors/ignoreDuringBuilds bypasses. npm run build must exit 0.
Day 1 Gate: npx tsc --noEmit exits 0. Browser console shows 0 WebSocket errors at http://89.167.96.154:3002.
DAY 2: MINIMUM VIABLE FACTORY (DEVXIO)
Morning: LiteLLM + CI/CD
- TICKET_033: Verify LiteLLM proxy routing on Hetzner. Confirm Anthropic + Google Vertex endpoints respond. Add
cache_control breakpoint for Sonnet system prompts. Test token cost tracking via ccusage.
- TICKET_034: Create GitHub Actions workflow for STRUXIO_OS:
tsc --noEmit + npm run lint on PR. This is the CI/CD Guillotine — no code merges without passing.
Afternoon: WebSocket Bridge + Telemetry
- TICKET_035: Wire the FastAPI → Redis Pub/Sub → WebSocket → browser bridge so Screen 2 (Active Activities) shows live Sonnet execution logs. This is the Founder's eyes on the factory floor.
Day 2 Gate: LiteLLM routes a test prompt to Sonnet and returns a response. GitHub Actions blocks a deliberately broken PR. Live terminal output streams to the browser.
DAY 3: APPROVAL MATRIX + MVP RESEARCH (TRANSITION DAY)
Morning: Screen 7 (Approval Matrix)
- TICKET_036: Build the minimum viable Approval Matrix UI. Requirements: display pending tickets in State 1/2/3 queue, show the Architect's plan payload, two buttons:
[APPROVE] and [FLAG]. Data source: PostgreSQL tickets table (or a simple JSON file for now if DB isn't wired yet).
Afternoon: ISO 19650 MVP Deep Research & Architecture
- Architect Session (Claude Opus 4.6): Using the STRUXIO Internal Blueprint and the MVP_01 service blueprint as inputs, I will produce:
BLUEPRINT_MVP_ISO19650_v1.0.md — Full technical architecture for the compliance service
- The 15-minute wizard data schema
- BEP/EIR generation logic specification
- Odoo module mapping (which apps to install, what custom addons are needed)
- Stripe integration spec
- Odoo Website landing page structure
Day 3 Gate: Approval Matrix renders and shows a test ticket. MVP architecture document is complete and approved by Founder.
DAY 4: MVP BACKEND (ISO 19650 ENGINE)
Morning: Odoo Configuration
- TICKET_037: Install and configure Odoo modules on Odoo.sh: Documents (CDE backbone), Project (MIDP/TIDP tracking), Approvals (state transition gates), Website, CRM, Subscriptions. Configure the 4-state CDE workflow (WIP → Shared → Published → Archived).
Afternoon: BEP/EIR Generator
- TICKET_038: Build the Python backend logic that ingests wizard data and generates formatted BEP/EIR Markdown documents. Input: project metadata JSON from the wizard. Output: compliant BEP document following ISO 19650 Part 2 Annex A structure. Deploy as a FastAPI endpoint on the Hetzner backend.
Day 4 Gate: Odoo CDE shows the 4-state workflow. A test API call to the BEP generator returns a valid document.
DAY 5: MVP FRONTEND (WIZARD + LANDING PAGE)
Morning: The 15-Minute Wizard
- TICKET_039: Build the client onboarding wizard. Multi-step form: project metadata → stakeholder abbreviations → LOIN requirements → delivery milestones. On submit, calls the BEP/EIR generator API. Displays the generated documents for review. Can be built as an Odoo Website page or a standalone Next.js component — Architect to decide based on Day 3 research.
Afternoon: Landing Page + Stripe
- TICKET_040: Build the marketing landing page on Odoo Website. Key sections: problem statement, the 3-step solution, pricing ($3,000 setup + $500/mo), social proof placeholder, CTA button. Integrate Stripe checkout for the $3,000 setup fee. Connect Odoo Subscriptions for the $500/mo recurring.
Day 5 Gate: A test user can complete the wizard, see generated BEP/EIR documents, and complete a Stripe test payment.
DAY 6: MVP INTEGRATION + MARKETING AUTOMATION
Morning: CDE Auto-Provisioning
- TICKET_041: On successful Stripe payment, automatically provision a new Odoo CDE project for the client. This means: create the project in Odoo Project, set up the folder structure in Odoo Documents with the 4-state workflow, and send the client an onboarding email with their CDE access credentials.
Afternoon: The Wedge Marketing Engine
- TICKET_042: Build the lead generation pipeline:
- Python scraping script targeting LinkedIn/Indeed for AEC firms with "BIM Manager" or "Information Manager" roles open >30 days
- Apollo.io API integration for lead enrichment (verified emails for Directors)
- Cold email templates loaded into Odoo Email Marketing
- Sequence: Day 1 intro → Day 3 follow-up → Day 7 case study
Day 6 Gate: End-to-end test: fake Stripe payment → CDE auto-provisioned → client email sent. First batch of 50 enriched leads loaded into Odoo CRM.
DAY 7: LAUNCH PREP + FIRST OUTREACH
Morning: DNS + SSL + Polish
- TICKET_043: Configure Porkbun DNS for:
struxio.ai → Odoo Website (landing page + wizard)
app.struxio.ai → Odoo.sh CDE portal (client-facing)
factory.struxio.ai → DEVXIO portal on Hetzner (internal)
- SSL certificates via Let's Encrypt / Odoo.sh built-in SSL
Afternoon: Go Live
- Final QA pass on the full flow (wizard → BEP generation → payment → CDE provisioning)
- Launch cold email sequence to first 50 leads
- Publish LinkedIn announcement from STRUXIO corporate page
- Founder manual outreach to 10 warm contacts in Israeli AEC market
Day 7 Gate: struxio.ai resolves to the live landing page with working Stripe checkout. First 50 cold emails sent. The ISO 19650 compliance service is open for business.
POST-SPRINT OPERATING MODEL
After Day 7, the team enters a dual-track cycle:
- Revenue Track: Close first 5 clients. Iterate on the wizard based on feedback. Build the AI Compliance Auditor (Phase 2 feature).
- Factory Track: Resume DEVXIO improvements as needed — add Screens 3-6, wire Qdrant for semantic search, build the Bootstrap Gate. These are now funded by client revenue, not burning runway.
SUBSCRIPTION DECISIONS
| Service |
Cost |
Decision |
Rationale |
| Odoo.sh |
Already active |
KEEP |
CDE backbone + website + CRM |
| Apollo.io |
$49/mo |
ADD |
Lead enrichment for Wedge strategy. Odoo CRM can't find leads. |
| Vercel Pro |
$20/mo |
SKIP |
Odoo Website handles the landing page |
| Hetzner CPX32 |
Already active |
KEEP |
DEVXIO backend + FastAPI + LiteLLM |
Total new spend: $49/month (Apollo.io only)
— STRUXIO.ai // 7-Day Blended Sprint v1.0 // Generated by Claude Opus 4.6 (Principal Architect) // © 2026