AIITech Year 1: The 20%
Precision Execution Map
The Operating Principle
The full business plan documents 44+ microservices, 4 verticals, 6
service lines, a PSA SaaS product, an RPA practice, managed services
tiers, advisory offerings, a WordPress site, a React dashboard, an
admin backend, and an XPRIZE quantum research submission. That's
the 5-year vision. Year 1 is about doing six things well, not forty-four
things partially.[1][2][3]
The 20% that generates 80% of Year 1 value:
  1. One sellable automation service (not four verticals)
  2. One functional PSA MVP (not a full platform)
  3. Pipeline that converts (not marketing that broadcasts)
  4. Paying pilots (not perfected products)
  5. Reusable delivery assets (not custom everything)
  6. Managed services contracts (not one-off projects)
Everything else waits.


What to Build: 6 Microservices, Not 44
The microservices catalog lists 44+ services across PSA core,
automation/RPA, agentic AI, verticals, integrations, and governance.
For Year 1, you build six. These are the minimum viable backend to
support both the PSA demo and automation service delivery:[3]
 Pri
         Microservic                                        Build
 orit                          Why It's Essential
              e                                             When
  y
         Identity &      Authentication, RBAC, tenant
                                                            Mont
 1       Access          isolation—nothing works
                                                            h 1–2
         Service         without it
         Project/Eng     Projects, tasks, milestones,
                                                            Mont
 2       agement         status workflows—the PSA's
                                                            h 1–3
         Service         identity [4]
         Time &          Timesheets, approvals,
                                                            Mont
 3       Expense         utilization metrics—core PSA
                                                            h 2–3
         Service         value prop
                         Invoice generation from
         Billing/Invoi                                      Mont
 4                       time/fees, sync to QuickBooks—
         cing Service                                       h 3–4
                         the money path [4]
         Automation      Single API façade to invoke
                                                            Mont
 5       Execution       automations—bridges PSA to
                                                            h 4–5
         API             RPA delivery [3]
         Reporting/A     Margin, utilization, burn
                                                            Mont
 6       nalytics        dashboards—what clients and
                                                            h 5–6
         Service         you need to see value

What Explicitly Does NOT Get Built in Year 1
     No Bot Orchestration Service (use UiPath/Power Automate
     native orchestration)
     No Document Understanding/RAG services (partner with ABBYY
     or use LLM APIs directly)
     No vertical-specific microservices (healthcare, manufacturing,
     BFSI modules are Year 2)
     No Process Mining Discovery Service
     No Knowledge Retrieval RAG Service
     No Natural-Language Command Service
     No multi-region deployment, no API gateway/developer portal
     No Feature Flag/Experimentation Service
You don't build what you can borrow, partner for, or defer.


Sprint 1: Months 1–3 (March–May 2026) —
Foundation
The Only Goal
Stand up a demonstrable PSA prototype and draft your first pilot
SOW.

Do This
Product (Ruth-led)

     Connect the React/TypeScript dashboard to real APIs—replace
     the mock data in App.tsx[2]
     Implement QuickBooks OAuth and Salesforce OAuth—these are
     the two "central pieces" Ruth already identified[2]
     Build Identity & Access + Project/Engagement + Time & Expense
     services as lightweight APIs (Node.js Express, since it matches
     the stack)[4][2]
     Deploy on Vercel ($20–25/mo) or Google Cloud pay-as-you-go[2]
     Target: clickable PSA prototype with real data flowing by end of
     Month 3[5]
Services (Ryan-led, 10–20 hrs/week)

     Complete 1 UiPath or Power Automate certification[1][5]
     Build 3–5 demo automations tied to PSA use cases: timesheet
     reminders, invoice generation, data sync to accounting[5]
     Create the standard delivery playbook: discovery template, SOW
     template, success criteria checklist[5]
Pipeline

     Identify 25 target accounts from warm network (not 50–100—be
     realistic with available hours)[1]
     Schedule 5 discovery calls[1]
     Draft 1 pilot SOW ($25K–$35K, reduced rate, single process)[5]
Business Foundation
    Legal entity formation, E&O insurance, service agreements
    finalized[1]
    GitHub repos organized: AIISTECH-Website, AIISTECH-
    Dashboard, AIISTECH-Backend[2]

Do NOT Do This
    Do NOT discuss Workato vs. Zapier vs. Make.com vs. n8n vs.
    Tray.ai —there are no clients to integrate for yet[2]
    Do NOT build vertical modules (healthcare, manufacturing
    pages) —you have no vertical clients yet[2]
    Do NOT work on the XPRIZE quantum submission during
    AIITech sprints—timebox it separately
    Do NOT evaluate Google AI Studio vs. Vertex AI for integration —
    premature optimization[2]
    Do NOT design the WordPress client-facing website —a landing
    page with a Calendly link is enough[6]

Sprint 1 Decision Gate (End of Month 3)
     Metric               Pass                  Fail/Pivot
 PSA prototype                          ❌ Still on mock data →
                    ✅ Connected to
 live with real                         stop adding features, fix
                    QB/SF
 API data                               the pipeline
 Demo                                   ❌ <3 → deprioritize PSA,
                    ✅ 3–5 working
 automations                            focus on services-only
                    demos
 built                                  model
                    ✅ 5+ discovery
 Pipeline                               ❌ 0 calls → pivot outreach
                    calls, 1 SOW
 generated                              strategy immediately
                    drafted
                                        ❌ Incomplete → nothing
 Legal/business
                    ✅ Complete          else matters, finish this
 formation
                                        first
Sprint 2: Months 4–6 (June–August 2026) —
First Revenue
The Only Goal
Land 2 paying pilots and get the PSA into beta users' hands.

Do This
Product

     Harden PSA workflows: projects, time, invoices, basic
     dashboards[5]
     Build the Billing/Invoicing Service—this completes the money
     path (time → invoice → QuickBooks sync)[4]
     Add CSV export as your only "integration"—no Salesforce CRM
     sync, no NetSuite, no HubSpot yet[5]
     Get 5–10 real teams using the PSA beta. Instrument telemetry:
     what they use, what they ignore, where they drop off[5]
Services

     Run 2 paid pilots ($25K–$50K each, fixed-price, single process
     per pilot)[1]
     Each pilot automates exactly 1 process: invoice processing,
     claims intake, or report generation[5]
     Over-invest in documentation and client training for each pilot—
     each one becomes a case study[5]
     Start the reusable component library: common UiPath activities,
     document templates, PSA API client[5]
Pipeline

     Launch the Automation Readiness Assessment as your primary
     CTA—this is a $2,500 refundable workshop[1]
     Convert pilot clients toward Phase 4 full implementation
     discussions[1]
     Hire: junior delivery consultant + part-time sales/BD
     (commission-based initially)[1]
Revenue Target: $60K–$111K cumulative[1]
    Q1 (retrospective): ~$50K (pilots + small PSA)
    Q2: ~$111K (pilots completing + first implementation starting)

Do NOT Do This
    Do NOT add AI features yet (no smart time suggestions, no NLP
    task creation, no anomaly detection) —that's Month 7+ after you
    have users giving feedback[5]
    Do NOT launch managed services tiers—you have no completed
    implementations to manage
    Do NOT pursue enterprise ($5K+ employee) accounts—stick to
    mid-market ($50M–$200M revenue)
    Do NOT build the Automation Execution API yet—use direct
    UiPath/Power Automate orchestration for pilots
    Do NOT hire a PSA product manager—too early, Ruth owns
    product until there's revenue to justify the role

Sprint 2 Decision Gate (End of Month 6)
 Metric              Pass                      Fail/Pivot
            ✅ 2+ pilots              ❌ 0 pilots → services model is
 Paid
            generating $60K+         not working, pivot to pure
 pilots
            revenue                  PSA or pure advisory
                                     ❌ <5 → product-market fit
 PSA
            ✅ 5–10 teams with        issue, do customer
 beta
            daily active usage       interviews before building
 users
                                     more
 Cumulat
                                     ❌ <$60K → extend runway
 ive        ✅ $100K+
                                     calculation, pause hiring
 revenue
                                     ❌ 0 → you can't sell without
 Case       ✅ 1–2 documented
                                     proof, prioritize
 studies    with ROI numbers
                                     documentation
            ✅ Decision made:
 Pick                                ❌ Still "all three" → force the
            healthcare OR
 ONE                                 decision based on pilot client
            manufacturing OR
 vertical                            data
            BFSI
Sprint 3: Months 7–9 (September–November
2026) — Productization
The Only Goal
Convert pilots into full implementations and create your first
repeatable offering.

Do This
Product

     Build the Automation Execution API—now you have real
     automation workflows to expose through it[3]
     Build the Reporting/Analytics Service—clients from pilots need to
     see ROI dashboards[3]
     Add first AI feature based on 3 months of user data: pick the one
     most requested (likely smart time suggestions or automated
     invoice generation)[5]
     Integrations v2: deeper QuickBooks sync (not just export, but
     bidirectional)[5]
Services

     Convert 1–2 pilot clients to full implementations ($100K–$150K
     each)[1]
     Create ONE productized offering for your chosen vertical:[5]
          If Healthcare: Prior Auth + Claims Intake Pack ($75K, 90-
          day deployment)
          If Manufacturing: Quality Control Automation Pack ($65K,
          75-day deployment)
          If BFSI: KYC/AML Starter Pack ($80K, 90-day deployment)
     Build the delivery kit for that one offering: requirements
     template, standard process map, test harness, docs[5]
Managed Services Launch

     Offer Bronze-tier bot monitoring ($2K–$5K/month) to completed
     pilot/implementation clients[1]
    Target: 2–3 clients on monitoring contracts generating $6K–
    $15K monthly MRR[5]
Pipeline

    Rebrand marketing around chosen vertical (e.g., "Healthcare
    Revenue Cycle Automation Specialists")[5]
    Publish 1 case study and 1 thought leadership piece per month
    Pursue 1–2 channel partnerships with MSPs or industry
    consultants[5]
Revenue Target: $140K this quarter ($280K cumulative H2 start)
[1]

Do NOT Do This
    Do NOT build a second vertical pack—validate the first one
    before duplicating
    Do NOT add CRM sync (HubSpot/Salesforce)—use CSV export +
    manual process
    Do NOT build the client-side dashboard blueprint yet—the PSA
    dashboard serves this role[7]
    Do NOT attempt agentic AI features (AI coordinator, exception
    reasoning, denial reasoning agents) —that's Month 13+[5]
    Do NOT pursue enterprise deals ($500K+)—conversion time is
    too long for Year 1 survival

Sprint 3 Decision Gate (End of Month 9)
    Metric              Pass                    Fail/Pivot
 Full           ✅ 1–2 converting       ❌ Pilots not converting →
 implement      from pilots            pricing or delivery quality
 ations         ($100K+ booked)        issue, investigate
                ✅ 1 packaged           ❌ Still custom everything →
 Productized
                vertical offering      you're a body shop, not a
 offering
                with clear pricing     product company
 MRR from                              ❌ $0 recurring → you're
                ✅ $6K+/month
 managed                               building a project business,
                recurring
 services                              not a recurring one
                                       ❌ <10 → PSA isn't finding fit,
 PSA paying
                ✅ 20+ teams            consider pivoting to
 customers
                                       services-only


Sprint 4: Months 10–12 (December 2026–
February 2027) — Scale Preparation
The Only Goal
Close Year 1 with revenue traction, recurring revenue foundation,
and a team that can handle Year 2 growth.

Do This
Product

    PSA v1 release: multi-entity support, time approvals, invoice
    status workflows, role-based dashboards[5]
    No new microservices. Polish and stabilize the 6 you have.
    Begin planning (not building) Integrations v3 and Automation
    Console for Year 2
Services

    Execute 1–2 more full implementations from pipeline
    Refine the productized vertical offering based on delivery
    experience—tighten scope, shorten timeline, improve margin[5]
    Document delivery methodology as a formal playbook
    (discovery → pilot → implementation → managed services →
    expansion)[5]
Managed Services

    Upgrade 1–2 clients from Bronze to Silver tier ($8K–
    $15K/month) as their bot count grows[1]
    Target: $10K–$15K monthly MRR by end of Month 12[1]
Team

    Hire full-time sales lead (the part-time BD person should be
    converting or replaced)[1]
    Hire 2nd delivery consultant to handle growing implementation
    load[5]
    Team target by Year 1 end: 5–6 FTE[5]
Series A Preparation (if pursuing)

    Pitch deck, financial model, customer references, cap table[1]
    Target: investor conversations Q1 2027 at $500K–$1M raise,
    $3M–$5M post-money valuation[1]
Revenue Target: $144K this quarter ($445K cumulative Year 1)[1]

Do NOT Do This
    Do NOT start Year 2 features early (no agentic AI, no multi-
    region, no partner ecosystem)
    Do NOT add a 2nd vertical offering until the first is validated
    with 3+ completed engagements
    Do NOT build the full admin backend blueprint —admin tooling
    for tenant management is Year 2[8]
    Do NOT expand to 3 marketing channels simultaneously—
    double down on whichever one generated leads in Sprint 2–3
The Year 1 "Ignore" List
These are explicitly documented in the project files but do not touch
in Year 1:

                                                When It Becomes
  Category          Deferred Items
                                                   Relevant
 Microser      38 of the 44 cataloged        Year 2–3 as revenue
 vices         services [3]                  justifies
                                             After 3+ completed
               2 of 3 verticals (pick one,
 Verticals                                   engagements in
               defer two)
                                             chosen vertical
                                             Month 13+ after
 Agentic       All 6 agentic AI
                                             managed services are
 AI            microservices [3]
                                             live
                                             Separate track entirely
 XPRIZE        QAHUS research
                                             —don't co-mingle
 Quantum       submission [2]
                                             hours
               Full client-facing website    Month 6+ when
 WordPres
               blueprint (100+ sections)     pipeline demands a
 s Site
               [6]                           conversion site
               Multi-tenant admin
 Admin                                       When you have 10+
               panel, RBAC management
 Backend                                     tenants to manage
               [8]
 Client        Full React/TypeScript
                                             Year 2 after PSA v1 is
 Dashboar      role-based dashboard
                                             stable
 d             blueprint [7]
 Integrati     CRM, Calendar, API
                                             Year 2 when clients
 on            Gateway, Usage Metering
                                             demand it
 Platform      services [3]
               Tenant Policy, Feature        Year 2+ when you
 Governan
               Flags, Schema Migration       have compliance
 ce
               services [3]                  requirements
Ruth and Ryan: Role Clarity for the 20%
Based on the conversation dynamics and stated availability:[2]
Ruth (Full-time focus)

    Owns: PSA product development (the 6 microservices),
    dashboard, QB/Salesforce OAuth integration
    Owns: Architecture decisions (Node.js Express BFF, deployment
    to Vercel/GCP)
    Owns: Client onboarding, beta user management, product
    telemetry
    Does NOT own: automation demo builds, RPA certifications, or
    Tray.ai competitive analysis
Ryan (10–20 hrs/week)[2]

    Owns: UiPath/Power Automate certification and demo
    automation builds
    Owns: Pilot delivery (the actual automation engineering on
    client sites)
    Owns: Delivery playbook, SOW templates, success criteria
    frameworks
    Owns: Technical review of Ruth's architecture work (weekly
    sync)
    Does NOT own: PSA feature development, website design, or
    marketing content
Shared

    Pipeline/sales: Both reach into networks. Ruth handles inbound;
    Ryan handles technical discovery calls
    Vertical selection decision: Made jointly at Sprint 2 decision gate
    based on pilot data
    Hiring: Joint decision on junior consultant (Month 2–3) and part-
    time sales (Month 4)
The Year 1 Financial Spine
Stripped to what matters for cash survival:[1]

                Reven         Cash
  Quarter                                  Cumulative Position
                 ue           Burn
 Q1 (Mar–                    -$35K
                $50K                   Surviving on initial capital
 May)                        EBITDA
 Q2 (Jun–                    -$7K      Cash-flow neutral, pilots
                $111K
 Aug)                        EBITDA    paying off
 Q3 (Sep–                    +$7K
                $140K                  First positive quarter
 Nov)                        EBITDA
 Q4 (Dec–                    +$3K      Year 1 close: ~$445K
                $144K
 Feb)                        EBITDA    revenue, -$32K net

The critical survival moment is Month 4–6. If pilots don't land by
Month 6, the $100K–$150K initial capital runs out by Month 8–9. The
entire Year 1 plan hinges on the Sprint 2 decision gate.

The One Sentence That Governs Everything
Ship the PSA MVP with 6 microservices, land 2 paid automation
pilots in your chosen vertical, convert them to managed services,
and document everything as reusable assets—then stop and
assess.

Everything else is Year 2.
