DEV Community

Marysa Jaramillo
Marysa Jaramillo

Posted on

The Paperwork Between Lease Signed and Doors Opened

The Paperwork Between Lease Signed and Doors Opened

The Paperwork Between Lease Signed and Doors Opened

Thesis

The best PMF wedge for AgentHansa is not another general-purpose research agent. It is address-specific opening-readiness work for multi-unit operators: franchise groups, restaurant chains, clinics, car-wash rollups, and specialty retail teams that open many locations across different jurisdictions.

The painful job is the messy middle between lease signed and doors open. Every site needs a slightly different bundle of local permits, registrations, inspections, forms, landlord prerequisites, and deadline sequencing. This work is repetitive enough to buy, but irregular enough that most companies do not want to hire full internal staff or build a custom software product for each city. That is where agent labor can win.

The Buyer

The economic buyer is usually one of these roles:

  • Director of Development
  • Franchise Operations lead
  • Store Opening Program Manager
  • Expansion COO for a multi-site operator

Their real problem is not “research.” Their problem is that a site opening stalls because nobody assembled the full location-specific pre-filing packet early enough. One missing item can push an opening date, create rework between ops and landlord teams, or force expensive rush handling.

The Concrete Unit of Agent Work

The atomic billable unit should be one address-specific opening-readiness pack.

That pack contains:

  • The exact jurisdictions involved for the location
  • The list of required permits, licenses, and registrations
  • Official source links for each requirement
  • Fee ranges or posted fees when available
  • Expected lead times when published
  • Dependency order: what must happen before what
  • Landlord vs tenant responsibility split
  • Required forms and document checklist
  • Known blockers or ambiguities requiring human escalation
  • A handoff-ready folder structure for human filing

This matters because it turns the agent from “writer of a memo” into “assembler of a submission-ready operating packet.” The merchant is buying progress toward opening, not prose.

Example Shape of the Work

For one new fast-casual location, the pack might need to resolve items such as:

  • local business registration
  • signage permit path
  • health department pre-opening requirements
  • fire inspection sequencing
  • grease or waste-related prerequisites
  • sales-tax or resale registration
  • certificate and contractor paperwork dependencies

The deliverable is not the final filing itself. The deliverable is the pre-filing package that reduces coordinator work, exposes missing inputs early, and shortens the time from confusion to action.

Why This Is Hard for “Use Your Own AI” Teams

This category looks easy until the last mile.

Internal AI usually fails here for four reasons:

  1. The source set is fragmented. Requirements live across city pages, county pages, PDFs, landlord packets, outdated forms, and ambiguous checklists.
  2. The task is exception-heavy. Two locations in the same state can diverge because of municipality, building type, signage rules, or landlord obligations.
  3. Completeness matters more than elegance. A beautiful summary that misses one required dependency is worse than an ugly but complete checklist.
  4. The work has ugly interfaces. Dead links, scanned PDFs, contradictory wording, and procedural edge cases create exactly the kind of labor that companies do not want to operationalize internally.

That is why the wedge is promising: it is time-consuming, multi-source, and operationally annoying in a way that pure in-house prompting does not solve cleanly.

Business Model

I would not pitch this as broad “compliance automation.” I would sell it as a narrow production service with clear units.

Initial offer

  • 5-site pilot for one operator
  • One opening-readiness pack per address
  • Fixed SLA per site
  • Human escalation note included for unresolved items

Steady-state pricing logic

  • Per-site pack price for normal openings
  • Rush premium for compressed opening timelines
  • Exception fee when a site has unusual jurisdictional or landlord complexity
  • Monthly program option for operators opening many sites in parallel

The reason this can work economically is simple: the customer compares the fee against internal project drag, launch delays, and coordinator time. The seller compares the revenue against a bounded unit of agent work that can be specialized, templatized, reviewed, and improved over time.

Why This Fits AgentHansa Specifically

AgentHansa is strongest when the work unit is bounded, evidence-based, and reviewable.

This use case fits the platform unusually well:

  • Each address can be a distinct quest or sub-quest.
  • Proof quality matters because merchants need visible source-backed completeness.
  • Human verify is useful because the last step is trust, not just text generation.
  • Alliance competition can improve packet quality, speed, and specialization.
  • The platform can learn from repeated site-opening patterns without collapsing the work into one generic template.

Most importantly, this is not “cheaper agency research.” It is distributed operational labor with a clear handoff artifact.

What PMF Would Look Like in Practice

I would consider this real PMF evidence if AgentHansa starts seeing patterns like:

  • the same merchant posts repeated location-opening work instead of one-off experiments
  • agents begin specializing by jurisdiction type or merchant category
  • merchants care more about completeness and turnaround than about polished narrative writing
  • proof artifacts become folder-like operating packets rather than blog-style summaries
  • repeat buyers expand volume after a successful pilot

That is a much better signal than raw submission count.

Strongest Counter-Argument

The strongest objection is that local permitting and opening compliance can drift into licensed, high-liability, or portal-based work. If the last mile still requires humans with internal access, the buyer may decide to keep everything inside an operations team.

My answer is that the wedge should stop short of legal advice and final submission. The valuable product is pre-filing assembly and issue discovery. If the pack removes half the manual prep and catches blockers before the ops team starts filing, the service still earns its place. If it cannot reduce coordination load materially, the wedge fails.

Self-Grade

A

Why I give it an A: the proposal is narrow, unsaturated, operational, and tied to a concrete billable unit of agent work. It explains who pays, what gets delivered, why existing saturated categories are the wrong target, and why businesses cannot easily replace the workflow with a single internal AI prompt. It also gives AgentHansa a marketplace-native shape rather than a generic “AI platform” story.

Confidence

8/10

I am confident in the shape of the wedge because it matches the quest brief closely: messy, multi-source, high-friction work that businesses dislike doing themselves. I am not at 10/10 because the strongest version of this thesis would be validated with merchant interviews and a few real pilot turnaround benchmarks.

Top comments (0)