top of page

Everyman Brand Archetype

Automotive

Project Management Software

Part3

Won architecture and engineering firms by digitizing construction administration—submittals, RFIs and field reports—into one accountable project record, despite email, spreadsheets and legacy AEC document systems.

• BUSINESS MODEL

• REVENUE

• MARKET TYPE

• MARKET ENTRY

• GROWTH MODEL

• MOAT

• EDGE

• FOOTHOLD

1

MODEL

Part3 addressed a frequent, high-consequence workflow in architecture and engineering: construction administration. Architects and engineers managed submittal reviews, RFIs, field reports and project correspondence across email, spreadsheets and legacy tools. Part3 centralized these workflows into one project record, reducing missed deadlines, version confusion and accountability gaps. Founded in 2021, it raised a $2 million seed round in July 2023 from investors including 519 Growth Fund, Astanor Ventures, Hyde Park Venture Partners, Talis Capital and Bart Swanson. Its AI-powered tools automate review and documentation tasks, targeting the administrative burden that delays projects and increases professional risk.

Question this model answers

We need to prove that customers have an urgent problem.

BUSINESS MODEL

SaaS

HOW THEY BUILT IT

'- Construction-administration wedge: Part3 began with submittal reviews, RFIs and field reports—the administrative core of architecture and engineering project delivery.

- Single project record: The platform centralized correspondence, decisions, documents and deadlines into one accountable system.

- Role-based workflow: Architects, engineers, contractors and consultants could operate within a shared project structure.

- AI-assisted review: AI tools automated repetitive review, documentation and administrative tasks.

- Vertical SaaS subscription: Firms paid recurring subscriptions based on users and project usage.

- Risk-reduction positioning: Part3 sold reduced missed obligations, better documentation and lower professional liability exposure.

HOW TO ARCHITECT IT

1. Find a regulated or high-liability workflow buried in email. Identify a process where missed deadlines, version errors or undocumented decisions create financial or professional risk.

2. Digitize the record before adding intelligence. Build a structured system for documents, decisions, deadlines and accountability before applying AI.

3. Map the real workflow, not the org chart. Understand how architects, engineers, contractors and consultants actually exchange information.

4. Make compliance the default. Build audit trails, deadlines and role accountability into the workflow rather than treating them as reports.

5. Expand from one document type to the project lifecycle. Add RFIs, field reports, meetings or closeout only after the first workflow becomes the project’s system of record.

DISTRIBUTION MODEL

Direct Sales, Community-Led, Content Marketing, Partnerships

HOW THEY OPERATIONALIZED

'- Direct sales to architecture and engineering firms: Part3 sold to principals, project managers and construction-administration leaders responsible for project risk.

- AEC community engagement: Industry events, professional networks and architecture communities created access to design-firm buyers.

- Content on construction administration: Material on RFIs, submittals and project risk educated firms on the cost of fragmented workflows.

- Design-partner referrals: Early architecture and engineering customers provided credibility within a relationship-driven industry.

HOW TO REPLICATE WHAT WORKED

What Worked

Sell to the person accountable for professional risk, then use a narrow document workflow as the entry point into the broader project record; vertical communities and referrals matter when trust and reputation drive adoption.

Trap if Copied Blindly

Vertical SaaS sales fail when the buyer’s existing process is deeply embedded in email and legacy tools; without migration support and a clear risk-reduction outcome, firms will not change workflow.

Insight on Untapped Business Model / Gaps / Pitfalls

GOLDMINE

GOLDMINE 1 — AI CONSTRUCTION-ADMINISTRATION AGENT. The opportunity is not another document repository but an agent that reads submittals, flags deviations, drafts responses and tracks open obligations. The winner will combine structured project data with domain-specific review logic.

GOLDMINE 2 — CROSS-PARTY PROJECT RECORD. Most tools serve one party; the gap is a shared record across architect, engineer, contractor and owner. A neutral system of record can reduce disputes and improve accountability.

GOLDMINE 3 — RISK AND COMPLIANCE ANALYTICS. The opportunity is to identify late submittals, repeated RFIs, scope drift and documentation gaps before they become claims. Risk analytics can justify premium pricing.

THE TRAP TO WATCH

THE PIT — DOCUMENT STORAGE WITHOUT WORKFLOW. A repository does not create accountability; the product must manage deadlines, roles and decisions.

THE SECOND PIT — AI REVIEW WITHOUT DOMAIN CONTEXT. Generic AI can misread drawings, specifications or contractual obligations; AEC-specific training and human-in-the-loop review are necessary.

MOVE WITH CAUTION

Do not enter AEC software by promising to “digitize construction.” Start with one high-liability workflow, prove adoption by project managers, then expand across the project lifecycle.

2

MARKET

MARKET TYPE

Fragmented Market

WHY THEY WON

Construction administration was fragmented across firms, project types, geographies and tools. Architects, engineers and contractors used different systems, while much of the workflow remained in email and spreadsheets. Part3 exploited the gap by creating a vertical system of record for the design team’s construction-administration obligations. The transferable lesson is that fragmented industries reward entrants that standardize one high-liability workflow before attempting to connect every participant.

Part3 entered construction administration, where architects and engineers often managed submittals, RFIs and field reports through email, spreadsheets and legacy document systems. The old process relied on manual tracking, attachments and individual inboxes; the adoption barrier was fragmented workflows and established professional habits. Part3 sold the operational outcome: a centralized, accountable project record with fewer missed obligations and better documentation.

Question this model answers

We need to enter a traditional or under-digitized industry.

ENTRY STRATEGY

Greenfield Entry

EXECUTION

Part3 entered by creating a new construction-administration platform rather than replacing an established project-management system. The initial bet was that architecture and engineering firms would adopt a dedicated system for submittals, RFIs and field reports if it reduced risk and administrative burden. This was viable because Part3 could start with one firm or project team and deliver standalone value. The essential prerequisite was a structured project record; the approach would fail if the platform merely stored documents without managing workflow.

FOOTHOLD STRATEGY

Beachhead Strategy

THE HOW

Part3’s first beachhead was architecture and engineering firms responsible for construction administration. The pain was missed submittal deadlines, fragmented RFIs and weak documentation; principals and project managers were reachable through AEC communities and direct relationships. They could pay because better documentation reduced professional risk and administrative burden. From construction administration, Part3 could expand into broader project delivery, field operations and owner collaboration.

MARKET TYPE PLAYBOOK

RULE 1 — START WITH ONE PROFESSIONAL ROLE. The architect or engineer responsible for construction administration feels the pain most directly.

RULE 2 — CREATE A STRUCTURED RECORD. Documents, decisions and deadlines must become data before AI or analytics can add value.

RULE 3 — SELL RISK REDUCTION. Professional liability and missed obligations create stronger willingness to pay than convenience alone.

RULE 4 — KNOW WHEN MULTI-PARTY ADOPTION IS REQUIRED. If contractors and owners must participate, the entrant may need a network or integration strategy.

In a fragmented market, the entrant wins by standardizing one high-liability workflow and becoming the trusted record for that workflow.

GENERAL RULES

WHAT HAPPENS IN THIS MARKET TYPE

RULE 1 — Validate the liability being removed. The customer must understand the cost of missed deadlines, undocumented decisions or version errors.

RULE 2 — Build the structured record first. A workflow platform must capture documents, roles and decisions before adding AI.

RULE 3 — Start with one firm or project team. Bottom-up adoption reduces sales friction and creates a referenceable project record.

RULE 4 — Reject greenfield entry when multi-party adoption is mandatory. If contractors, owners and regulators must all participate, the entrant may need partnerships or network effects first.

Greenfield entry is appropriate when the company creates a new digital workflow for a manual, fragmented or under-digitized process.

A beachhead works when one customer group has a concentrated, high-liability pain and the vendor can prove reliable workflow value.

HOW TO APPLY FOOTHOLD STRATEGY

RULE 1 — Target the accountable professional. Architects and engineers responsible for construction administration feel the risk most directly.

RULE 2 — Start with one document workflow. Submittals or RFIs create a narrow, repeatable entry point.

RULE 3 — Measure deadline compliance and documentation quality. A beachhead is working when firms reduce missed obligations and improve project records.

RULE 4 — Expand through the project lifecycle. Once one workflow is habitual, field reports, meetings and closeout become natural adjacencies.

Expanding across the full construction lifecycle before the construction-administration record becomes habitual.

HOW TO APPLY MARKET ENTRY STRATEGY

Part3 entered construction administration directly; a failure pattern is building a platform that requires all project parties to adopt before delivering value.

PATTERNS OF THIS MARKETING MODEL

PATTERNS IN VERTICAL COMMUNITY-LED SAAS WITH DIRECT SALES:

1. Professional communities create trusted access. Architecture and engineering networks influence tool adoption.

2. Risk-based content attracts accountable buyers. Material on RFIs, submittals and liability reaches the person who owns the consequence.

3. Early customer references reduce perceived risk. Design firms rely on peer proof before changing project workflows.

WEAKNESS

Vertical community sales can be slow; without a clear workflow wedge and outcome evidence, relationships do not become repeatable revenue.

GROWTH CAMPAIGNS

'- Construction-administration content on RFIs, submittals and field reports.

- AEC community engagement and industry-event presence.

- Design-partner and early-customer reference programs.

- AI-assisted review and documentation campaigns.

- Seed-stage direct sales to architecture and engineering firms.

- Project-risk and professional-liability positioning.

|  So What

Part3’s campaigns position the product around professional risk and administrative burden, not generic construction software.

|  Key Learning

The non-obvious principle is that vertical SaaS wins when it names the specific workflow whose failure creates liability, then becomes the system of record for that workflow.

|  How to Use

If you enter a traditional industry, identify the workflow where mistakes create legal, financial or reputational risk; build the record first, then add intelligence.

3

MONEY

REVENUE MODEL

Subscription, Service Fee

Part3 validated willingness to pay by converting architecture and engineering firms from email-and-spreadsheet workflows into a paid project-record platform. Firms paid for structured submittal reviews, RFI management, field reporting and AI-assisted documentation. The value was reduced administrative burden, improved accountability and lower professional risk—not merely document storage.

Question this model answers

We need to validate whether people will pay.

PRICING STRATEGY

Flat Rate Pricing, Tiered Pricing, Value-Based Pricing

WHY THEY WON

Architecture and engineering firms pay recurring subscriptions for project users and construction-administration workflows. Revenue expands with users, active projects and AI or premium modules. Software delivery supports strong gross-margin potential, though onboarding, data migration and customer success create service costs in a relationship-driven industry.

TARGET AUDIENCE

Architecture firms (want structured submittal reviews and project documentation); engineering firms (want RFI and field-report accountability); project managers (want deadlines, decisions and audit trails); principals (want reduced professional liability); multi-office design firms (want consistent construction-administration standards).

Part3 uses subscription pricing for architecture and engineering firms, with plans likely based on users, projects and feature access. The buyer pays for a structured construction-administration system rather than a per-document fee. Enterprise or multi-project pricing can expand with firm size and AI adoption.

CUSTOMER BUYING BEHAVIOUR

The trigger is a new project, audit, professional-liability concern, missed submittal or operational inefficiency. Project managers evaluate through demos, pilot projects and peer references; principals approve when the platform reduces risk. Adoption expands from one project team to firm-wide standards.

WILLINGNESS TO PAY

CORE INSIGHT

Firms are not buying construction software; they are buying protection against missed obligations and undocumented decisions.

RULES OF ADOPTION

RULE 1 — PRICE PROFESSIONAL RISK REDUCTION. The relevant alternative is not another app but a claim, delay or reputational damage.

RULE 2 — PRICE THE PROJECT RECORD. Users and active projects reflect the scale of work being governed.

RULE 3 — SELL ACCOUNTABILITY, NOT STORAGE. Deadlines, roles and audit trails create value beyond document management.

RULE 4 — WATCH THE AI-INPUT TRAP. AI review is only valuable when the underlying project data is structured and reliable.

The buyer is really buying construction-administration certainty, proven by active projects, deadline compliance and documentation quality.

REVENUE RISK

Long sales cycles: Architecture and engineering firms can be slow to change established workflows, delaying revenue growth.

Multi-party adoption friction: Contractors, owners and consultants may use different systems, limiting end-to-end value.

Incumbent workflow inertia: Email, spreadsheets and legacy AEC tools are deeply embedded.

AI trust risk: Generic AI review can produce errors in drawings, specifications or contractual context, undermining confidence.

Project cyclicality: Construction activity and design-firm hiring can affect demand.

Part3 raised a $2 million seed round in July 2023; its ARR, churn and valuation are not publicly disclosed or independently verified.

4

MOTION

Part3 won early customers by targeting the professional accountable for construction-administration risk: architects and engineers managing submittals, RFIs and field reports. Direct relationships, AEC community engagement and design-partner references created trust in a relationship-driven industry. The $2 million seed round in 2023 supported product and go-to-market development while the company proved willingness to pay among design firms.

Question this model answers

We need our first paying customers.

GROWTH EXPANSION MODEL

Land & Expand, Product Line Expansion

HOW THEY EXPAND

Part3 landed through construction-administration workflows, then expanded within firms through more projects, users and AI-assisted review. Product-line expansion can extend from submittals and RFIs into field reports, meetings, closeout and owner collaboration. The dependency is the structured project record: expansion works when the first workflow becomes the firm’s accountable source of project truth.

COMPETITIVE STRATEGY

Community Growth

HOW THEY COMPETE

AEC communities and professional networks create awareness; project managers adopt the platform for one workflow; successful projects create references; firms expand usage across teams and projects. More project data improves AI review and risk insight. The loop depends on project-level value, peer trust and reliable workflow; weak adoption or generic AI output breaks it.

GTM

Part3 uses a community-led, sales-assisted GTM.

$5–10M ARR

AEC communities and professional networks create awareness; direct sales converts project managers and principals; customer success expands from one project to firm-wide adoption. The primary motion is community-led for trust, with direct sales converting risk-aware buyers into paying firms.

SUSTAINING MOATS

Data Advantage

The moat is Part3’s structured construction-administration data: submittals, RFIs, field reports, decisions and project timelines. Over time, this data can train domain-specific AI review, identify risk patterns and improve project documentation, making the platform more valuable than generic document storage.

|  Why This Moat Lasts

A data advantage lasts when the platform captures structured, high-liability workflow context that competitors cannot obtain without the same project record.

|  Standard Rules

RULE 1 — STRUCTURE THE SOURCE DOCUMENTS. Submittals, RFIs and decisions must become data before AI can add value.

RULE 2 — LINK RECORDS TO OUTCOMES. Deadline compliance, rework and claims make the data commercially valuable.

RULE 3 — USE DOMAIN-SPECIFIC AI. AEC review requires contextual understanding, not generic document processing.

|  The Signal

Part3 raised a $2 million seed round in 2023 and focuses on architecture and engineering construction administration. The moat does not protect against incumbent platforms adding similar workflows or a competitor that wins multi-party project adoption first.

ARR 
JOURNEY

Pre-$1M ARR

VALIDATE THE CONSTRUCTION-ADMINISTRATION WEDGE. Part3 launched in 2021 to centralize submittals, RFIs and field reports for architecture and engineering firms.

WATCH: Whether project managers would replace email and spreadsheets.

$1–5M ARR

PROVE RISK-REDUCTION VALUE. Part3 focused on project managers and principals who owned professional liability and documentation quality.

$5–10M ARR

EXPAND ACROSS PROJECT TYPES. The platform can extend from submittals and RFIs into field reports, meetings and closeout.

$10–50M ARR

ADD AI-ASSISTED REVIEW. Structured project data enables AI review, deviation detection and documentation automation.

$50–100M ARR

NOT REACHED / NOT PUBLICLY EVIDENCED. Part3 raised a $2 million seed round in 2023; its ARR is not publicly disclosed.

$100M+ ARR

NOT REACHED. The company remains in an early vertical-SaaS scaling phase.

BREAKDOWN

THE STANDARD

Build vertical SaaS by finding a high-liability workflow buried in email, creating a structured system of record, and adding AI only after the workflow data is reliable.

THE SEQUENCE

1. Find a workflow where mistakes create professional or financial risk. Identify submittals, claims, compliance files or approvals where missed obligations create real cost.

2. Build the structured record before intelligence. Capture documents, roles, deadlines and decisions in one accountable system.

3. Add AI to the structured workflow. Use domain-specific review and automation only when the record is reliable enough to trust.

Part3 focused on construction administration, where RFIs, submittals and field reports create professional risk and documentation burden.

THE CAUTION

Do not copy AI-first positioning without structured data; generic AI cannot reliably interpret specialized project context. Do not pursue multi-party adoption before proving value to the accountable professional—workflow change requires a clear risk-reduction outcome.

bottom of page