Auset Brain

testing-and-billing-model

2 min read

Testing & Billing Model — Every Heru

MVP Phase (Flat Fee)

Included (We Do)

  • Unit tests (agent writes with the code)
  • E2E tests — non-user, automated (Lorraine/Playwright)
  • Regression tests
  • Smoke tests
  • Performance tests (Core Web Vitals, load times)
  • Accessibility tests (WCAG)
  • Critical workflow tests (checkout, auth, booking, payment)
  • Bug fixes from Ida feedback during MVP — INCLUDED IN COST
  • Quality gate on every PR (type-check, lint, build, test)

Client Does (Their Responsibility)

  • UI testing on DEVELOP environment (not production)
  • Edge case discovery — report through Ida
  • Every screen must be approved through Ida to achieve MVP
  • Non-critical UI issues — they catch them, we fix (included in MVP)
  • They know their business and users — human judgment can’t be automated

Ida = MVP Gate Controller

  • Client reviews every screen on develop.heruname.com
  • Approve ✓ or Reject ✗ through Ida
  • Rejected screens get feedback → agents fix → redeploy → review again
  • Dashboard shows: X/Y screens approved
  • 100% approval = MVP certified = deploy to production
  • Screenshot auto-captured at approval time for audit trail
  • NO production deploy without full Ida sign-off

Post-MVP: Maintenance Contract (Monthly Retainer)

What’s Covered (SLA)

  • Production show-stoppers = OUR RESPONSIBILITY (part of maintenance fee)
    • Checkout broken
    • Auth not working
    • Payment failures
    • App crashes
    • Data loss
    • Any P0/P1 that blocks the business from making money
  • Response time SLA (e.g., 4 hours for show-stoppers)
  • Same pipeline: Ida report → agents fix → PR → deploy

What’s Extra (Per Feature)

  • New features beyond original scope
  • Back through the full pipeline: Granville → Maya → agents
  • Priced per feature with work order

Revenue Phases Per Heru

  1. MVP Build ($X flat) — everything above included, ends at Ida 100% sign-off
  2. Maintenance ($X/month) — production bugs, show-stoppers, SLA
  3. Feature Additions ($X/feature) — new capabilities beyond MVP scope

Why This Works

  • Client approves everything BEFORE production → no “this isn’t what I asked for”
  • Show-stoppers in production are our problem → client trusts us
  • Ida is the contract → screenshot proof of approval
  • Same swarm pipeline for MVP, maintenance, and new features → scales
  • Work orders show exactly what each agent did → transparency like a mechanic receipt

Graph View