Own Permit AI.

What you'd own.

Every artifact below transfers to your accounts on day one. The whole engine.

• ●Brand identity and positioning as Permit AI
• ●Landing page, demo flow, and customer-facing marketing collateral
• ●Founder persona, GTM playbook, and outbound messaging strategy
• ●Financial model and unit economics projections through year 3
• ●AI agent specification for permit identification and application writing
• ●Initial customer relationships and 30-day trial framework
• ●Stripe billing infrastructure and pricing tier architecture

What Roll Digital builds for you.

Custom scope to take Permit AI from MVP shell to operating business.

• ▸Permit jurisdiction database with automated updates across 3,000+ jurisdictions
• ▸FastAPI backend with Postgres for multi-tenant SaaS project management
• ▸Claude API integration for permit identification and application generation
• ▸Stripe billing system supporting $200-350 monthly subscriptions and trials
• ▸Email and Google OAuth sign-in for GC and architect onboarding
• ▸Customer portal with project dashboard and permit application export
• ▸30-day onboarding sequence and outbound GTM launch package

Why this could work.

The TAM is concrete: 75,000 GCs and architects spend $1,200 annually on permit-related tools. Your GTM is defined and low-CAC: cold outbound to a warm trade via LinkedIn and forums generates 20-30 demos monthly. The unit economics work at scale: 8 closes per month by month 6 gets you to $175k ARR mid-case. Permit delays cost GCs thousands in crew idle time, creating genuine pain that drives adoption.

What you'd risk.

Permit codes change constantly across 3,000+ jurisdictions, and maintaining accuracy is a full-time data operation. A single incorrect permit can cost a GC thousands in delay fees and lost contractor days, creating real liability exposure. GCs are relationship-driven and resistant to cold outbound. Procore, Buildertrend, and PermitFlow are already embedding permit features into ecosystems GCs already use. Standalone tools struggle against platform lock-in, especially when pricing is the only differentiator and word-of-mouth adoption moves slowly in construction.

Who this fits.

An experienced SaaS founder or agency owner with construction or architecture relationships. You understand GC pain points deeply, are comfortable executing cold outbound, and have technical chops or co-founder bandwidth to handle backend data operations. You understand CAC is high and LTV depends on retention at scale. You can execute the GTM playbook independently through month 6.

Timeline.

From contract signing to operating business.

1. Day 1
   Codebase, customer relationships, and founder knowledge transfer complete
2. Week 1
   Permit database schema designed, Postgres configured, Claude API tested
3. Week 3
   Authentication and Stripe billing integrated into FastAPI backend
4. Week 6
   Customer portal UI built, first trial users onboarded
5. Day 90
   Founder handoff complete, 2-4 trial customers acquired, scaling ready

Pricing.

Three ways in, depending on how much you want to build yourself.