// PlatformReportsPage.jsx — "Platform driven reports" (Algoma). // Native rebuild of the platform-driven-reports case study in the // lachler.com v4 design language. Platform track carries forest, manual // track carries orange — the two tracks converge on the export. const PR_PLATFORM_CHIPS = ['Address & parcel search', 'AI zoning report', 'GIS layer depth', 'Rent comps & market data', 'Demographics & permits', 'Site capacity / auto site plans', 'Pro forma modeling', 'Construction cost estimates', 'AI rendering', 'CAD export', 'One-click PDF export']; const PR_MANUAL_CHIPS = ['Custom site plans', 'Client product types', 'Unit mix breakdown', 'Amenity centers', 'Retention ponds', 'Parking & circulation', '3D axonometric views', 'Yield metrics (coverage, FAR, density)', 'Revision rounds', 'Presentation packaging']; const PR_PLATFORM_STEPS = [ ['Find the site', 'Address entry or Site Discovery search across parcels'], ['Confirm zoning & GIS layers', 'AI zoning report — FAR, height, setbacks, permitted uses — plus overlays and constraints'], ['Understand the market', 'Rent comps, demographics, building permit activity'], ['Run site capacity & renderings', 'Auto-generated site plans, parametric massing, AI renders'], ['Model the financials', 'Pro forma and construction cost estimates'], ]; const PR_MANUAL_STEPS = [ ['Lay out the site', "Client's pre-modeled product types placed on the parcel in Revit"], ['Confirm areas', 'Unit mix, coverage, FAR, and density validated'], ['Pull together presentation format', 'Site plan, axonometric views, metrics assembled by hand'], ['Run renders', 'Presentation-quality visuals for the concept'], ['Revise with the client', 'Multiple revision rounds via email and calls'], ['Package for client', 'Final branded PDF — 5–7 business day turnaround'], ]; const PR_PRINCIPLES = [ ['Export a presentation with data layers', "The export isn't a flat document. Each section is backed by a live data layer — zoning, capacity, market, renders — so the presentation stays connected to the analysis that produced it."], ['Build for the addition of platform services', "The presentation structure anticipates capability we haven't shipped yet. As new data and functionality land, they slot into the format — no rework, no redesign of the package."], ['Manual work is the spec', 'Design services stays ahead of the platform by definition. Each manual step it performs is catalogued, measured, and queued for automation in priority order.'], ['Meeting-ready is the bar', "The output must survive an investment committee without touch-up. If a user has to rebuild it in another tool, the export hasn't done its job."], ]; const PR_PHASES = [ { n: '1', status: 'Now', title: 'Build an expandable presentation format', body: 'Define the canonical presentation structure — cover, site summary, zoning, capacity, market, renders, yield metrics — as a modular format that accepts new sections without breaking existing ones.' }, { n: '2', status: 'Now', title: 'Add platform data as functionality lands', body: 'Each time the platform gains a capability, its output flows into the package automatically. The presentation gets richer with every release, on the same structure.' }, { n: '3', status: 'Next', title: 'Reduce manual assembly to zero', body: 'Move the assembly work itself into the product. This phase is demand-backed: customers consistently ask for editable assumptions over static reports, control of what data reaches the package, and white-label export — and the "Your Projects" initiative (Dashboard → Site → Design → Files → Export) is already scoped along these lines.', subs: [['3a', 'Host the presentation on the platform'], ['3b', 'Make it editable within the platform'], ['3c', "Host the user's product types"], ['3d', 'Toggle the specific data that makes it into the presentation'], ['3e', 'Custom export capabilities — PDF, CAD, and presentation formats']] }, { n: '4', status: 'Ongoing', title: 'Test with users, iterate, adapt, implement', body: 'Every phase ships to trial customers and design partners first. Their feedback reorders the queue — the roadmap follows observed demand, not assumption.' }, ]; const PR_METRICS = [ ['5–7 days', 'current design services turnaround per packaged concept — the manual baseline the export compresses'], ['1 click', 'from analysis to investor-presentation-ready PDF — the standard the export must hold'], ['31 : 1', 'opportunities evaluated per deal pursued — the volume the export has to keep up with'], ]; const PlatformReportsPage = ({ onNavigate }) => { const isMobile = (window.useIsMobile || (() => false))(768); React.useEffect(() => { const els = document.querySelectorAll('.reveal'); const obs = new IntersectionObserver(es => es.forEach(e => { if (e.isIntersecting) e.target.classList.add('visible'); }), { threshold: 0.08 }); els.forEach(el => obs.observe(el)); return () => obs.disconnect(); }); const chip = (manual) => ({ fontFamily: 'var(--ff-mono)', fontSize: '11px', padding: '6px 12px', borderRadius: '999px', background: manual ? 'rgba(212,90,27,0.07)' : 'rgba(61,84,72,0.08)', color: manual ? '#A34415' : ST.forest, border: `0.5px solid ${manual ? 'rgba(212,90,27,0.25)' : 'rgba(61,84,72,0.25)'}`, }); const Track = ({ title, tag, steps, manual }) => (
{title} {tag}
{steps.map(([b, s], i) => (
{i + 1}
{b} {s}
))}
); return (
{/* 01 About */} About Bridging the manual and the automated Today, Algoma produces two kinds of client-facing output. The platform generates preliminary site analysis on demand — parcel search, zoning confirmation, GIS layers, site capacity, renderings, one-click PDF export. Alongside it, our design services team builds fully customized site plans by hand: client-requested geometry, unit mix, amenity centers, retention ponds, and packaged yield metrics. The manual work is valuable precisely because it shows us what the platform should learn to do next. This case study maps that logic: which steps each track performs, where they converge, and the sequence for automating the gap.
Every step a human performs to package a presentation is a product spec waiting to be written.
{/* 02 The Logic */} The logic The platform needs to export a presentation that is meeting-ready A developer's real deliverable isn't a data layer — it's the document they carry into an investment committee, a lender meeting, or a client review. The platform already computes the substance. The remaining work is assembling that substance into a presentation without a human in the loop.
{[{ manual: false, h: 'What the platform does today', note: 'Everything needed for preliminary site analysis, on demand.', chips: PR_PLATFORM_CHIPS }, { manual: true, h: 'What design services adds by hand', note: "Custom concept work in Revit, driven by client-requested geometry and the client's pre-modeled housing products.", chips: PR_MANUAL_CHIPS }].map((c, i) => (

{c.note}

{c.chips.map(t => {t})}
))}
{/* 03 Two tracks */} Two tracks, one destination How the work happens now The same client outcome is currently produced two ways. Mapping both tracks step-by-step exposes exactly which steps are shared, which are automatable, and which still require judgment.
{!isMobile && ( )}
{/* 04 Principles */} Design principles Structure that supports growth
{PR_PRINCIPLES.map(([h, b], i) => (

Principle {String(i + 1).padStart(2, '0')}

{h}

{b}

))}
{/* 05 Sequence */} Sequence The automation path Four phases, ordered so that each ships value on its own while reducing the manual work required for the next.
{PR_PHASES.map((p, i) => (
{i < PR_PHASES.length - 1 && (
))}
{/* 06 Why it matters — dark band */}
Why it matters The presentation is where the platform earns the meeting

Developers evaluate dozens of opportunities for every deal they pursue. The teams that move fastest are the ones who can walk into a room with a defensible package the same day they find the site. Automating the export closes the last gap between analysis and decision.

{PR_METRICS.map(([v, l], i) => (
{v}
{l}
))}
); }; window.PlatformReportsPage = PlatformReportsPage;