End-to-end flow from intake through certification, delivery, invoicing, and close-out. Each node is a discrete SmartSuite status with clear entry/exit criteria. The 45-day triage path runs parallel for aging projects.
Portal Intake
Schedulers submit projects via the client portal. System parses permits, extracts SOW data. Submissions enter an admin approval queue before SmartSuite record creation.
PSoW / ABSoW Gate
Field tech confirms Permitted Scope of Work (PSoW) on arrival. If scope matches, it becomes ABSoW. If not, changes are recorded and revised list becomes the As-Built Scope of Work.
45-Day Triage
Projects exceeding 45 days since inspection transfer to the JES Triage account. Original scheduler loses portal access. GOA retains visibility. Invoices route to originating branch.
Record Counts
592 projects total
313 Ready for Cert
88 Certified
47 Closed
43 Field Complete
02Certification Pipeline
Swim-lane view showing handoffs between actors. The pipeline runs entirely on the VPS — no external services except Gmail for delivery, SmartSuite for state, and Stripe for billing.
VPS Pipeline
Entire pipeline runs on a single dedicated server. No cloud functions, no Zapier. HTML rendered via Jinja2, PDF converted by WeasyPrint, all stored locally.
10-Point Validation
Automated checklist: SOW completeness, photo requirements, drive log presence, RFI resolution, address verification, permit status, production days, and more. Auto-advances cert status on pass.
Certifier Routing
MD Anne Arundel → Diehl AIA
MD Montgomery → Diehl AIA
MD all other → Valerio PE
VA all → Valerio PE
CT all → Valerio PE
Triage Invoice Override
When a project is in JES Triage, invoices route to the originating branch — not the triage team. Reverse-lookup determines original account.
03System Architecture
Integration map of all services, connections, and data flow. The VPS is the operational center — SmartSuite holds state, Supabase mirrors it, Stripe handles billing, Gmail handles delivery, Google Calendar manages scheduling, and the client portal provides external access.
Single Server
All services run on one Hostinger KVM4 VPS. Caddy handles TLS termination and routing. Docker isolates the API and webhook containers.
Data Flow
SmartSuite is the source of truth. API reads/writes directly. Supabase mirrors every 5 minutes for read-heavy portal queries. Local SQLite handles auth and schedule changes.
Portal Architecture
React 19 SPA with role-based routing. 7 roles across 5 domains. Auth via SQLite with session tokens. 29 portal-specific API endpoints.
How certification packages and invoices are built, stored, and delivered. Both follow the same pattern: data aggregation from SmartSuite, template rendering via Jinja2, PDF conversion via WeasyPrint, local storage, and delivery via Gmail API.
Cert Modules
Each division has its own Jinja2 template module. UND generates SVG drive log charts. ANC/BRC produce per-unit tables. FND uses a component checklist. Modules compose into a single HTML document.
Overrides
The /cert-gen/approve endpoint accepts JSON overrides — corrections to auto-populated data. Overrides are saved alongside the cert for audit trail.
Invoice Pricing
Line items: SOW quantity x product unit price. Production day charges added for qualifying products. Trip charges added when applicable. Triage invoices route to originating branch.
Brand Logic
Inspection before 2026-01-01:
blackhouse. LLC branding
Inspection 2026-01-01+:
Unlikely Professionals
05Division & Product Matrix
Eight primary certification divisions plus add-on modules. Each division groups related products that share a common cert template pattern. Stacking order determines the sequence in which divisions appear on a multi-scope certification package.
Pattern Types
P1 — Per-unit with driving log. SVG aggregate chart generated from PSI/torque data. Only UND products.
P2 — Per-unit table. Each installed unit gets a row with location, dimensions, specs.
P3 — Checklist and compliance. Component list with pass/fail verifications.
Add-On Logic
Add-ons are auto-triggered by parent products. They never appear independently on a SOW. Backfill quantity equals the count of triggering parent products.
Flagged
FND and RTW divisions need deeper spec work. FND areaway and ABC components are undetailed. RTW entire module was skipped during the PSoW/ABSoW review session.
06Stakeholder & Integration Map
People, roles, systems, and how they connect. The zero-contact policy means property owners never interact with Unlikely — all communication flows through the general contractor accounts. The portal enforces role-based access across five domains.
Approval Chain
Dustin has final authority on certifications, invoices, intake approvals, and user management. Jacob handles day-to-day review, drafting, and payment reconciliation.
Field Interface
Darius operates entirely via WhatsApp. No portal login. Daily schedule sent as message. Photos and data returned via WhatsApp. PSoW/ABSoW gate happens on a mobile form.
Portal Roles
up_owner — full access, user mgmt
up_admin — everything except user mgmt
scheduler — intake, schedule, RFIs
goa — read-only certs + invoices
triage — scheduler powers, aged jobs
ssi — county form submissions
assistant — schedule assistant view
Brands
Pre-2026 inspections: blackhouse. LLC branding. Post-2026: Unlikely Professionals. Determined by inspection date, not generation date.