YardGuild

Roadmap

What we're working on next.

Three sections: what's in active dev, what's planned, and what we're listening for but haven't started. Items have honest gates — a thing might say "ship when 3 tenants ask" rather than "Q3." The promise is honesty, not a Gantt chart.

See /changelog/ for what we've already shipped.

Recently shipped (was on Next)

We do what we say we'll do

Next

In active development

Started or about to start. ETAs are best-effort, not commitments.

  1. Yards become foreign keys (assets + contracts scoped to a yard)

    Next 4–6 weeks

    We just shipped Yards as first-class entities (you can manage them at /counter/yards/) but they're a directory for now — assets and contracts still belong to the tenant globally, not to a specific yard. The next step is the data migration: add yard_id to Asset + Contract, set a default for existing rows, update create handlers to require/accept yard_id, filter the asset list + reports by yard. This is the change that turns Multi-yard from "three yard records you can edit" into "three actually-separate inventories."

  2. Notification preferences per role

    Next 4 weeks (was Soon — promoted now that Staff is live)

    Currently the daily 8am due-back SMS goes to the tenant's sms_contact_number and the 5pm overdue email to alert_email — same address for the whole tenant. Once tenants have multiple staff (which staff lifecycle now supports), owners want to route different alerts to different people. We'll add per-staff notification preferences (which alerts go to which person).

  3. Trial-end date stamped on the tenant — and "days left" surfaced everywhere

    Next 2 weeks

    Trial-end is now displayed on /counter/billing and via a 7-day CounterLayout banner. The next pass is making it more prescriptive: show "X days left of your 30-day trial" in the Counter header on every page (not just the last week), and add the date to /counter/settings + the weekly summary email.

Soon

Planned, not started

Coming after Next. Order may shuffle based on what paying tenants need.

  1. Outbound webhooks (your system → ours)

    Today our PayPal webhook receiver exists; outbound webhooks (e.g. notify your Zapier on a new contract or a damaged-return) are on the API page as roadmap. We'll add HMAC-signed delivery with retry + dead-letter, configurable per event type.

    Gate: Demand-gated — ship when 3+ Pro tenants ask for it

  2. Outdoor field signup (signup directly into a yard)

    Today every tenant gets the same self-serve signup. Some operators want a branded signup link they hand to a coworker so the coworker lands directly in the right tenant. We'll add tenant-scoped invite links — staff invite already exists via /counter/staff (shipped), this would be the public-facing variant.

    Gate: After Yards-as-FKs lands (so the link can pre-fill the yard)

  3. Per-tenant subdomains (acme.yardguild.app)

    Today tenants live at /counter/ behind the shared yardguild.com auth. Per-tenant subdomains would make link sharing cleaner and enable single-tenant SSO down the line.

    Gate: After 50 paying tenants

  4. Bug-report inbox (DDB-backed triage queue, not just email)

    The 🐞 button shipped 2026-05-26 sends bug reports as emails to hello@yardguild.com. Once volume is real, an admin-side /admin/bugs page with status + assignee + thread would beat triaging from inbox. Until then, email works.

    Gate: When email triage gets unmanageable (~20+ reports/week)

AI features

Gated behind revenue + data milestones

We're not chasing the AI demo trend. These ship when there's enough data + revenue for them to be useful and not embarrassing.

  1. Demand forecasting per asset category

    Predict utilisation by week, season, local events. Flag understock + overstock. Useful for owners deciding what to buy this season.

    Gate: Needs ≥12 months of per-yard rental history to be useful + ≥AUD $30k MRR before we invest engineering

  2. AI condition-photo damage detection

    Compare check-out vs check-in photos; auto-flag scratches, breaks, missing parts.

    Gate: ≥AUD $75k MRR. Consumer-dispute risk if the model misfires; needs strong baseline first.

  3. AI-drafted waiver / contract clauses

    LLM drafts of yard-specific terms within ACL / CCLA / ESIGN-compliant boundaries.

    Gate: ≥AUD $30k MRR + legal review for each market.

Listening

Gathering feedback

No commitment. Some of these we'll never build (and we'll say so honestly when we know).

  1. Xero / MYOB / QuickBooks direct integration

    Today we export GST/VAT/BAS as CSV in each market's accounting format — you drop the file into Xero / MYOB / QuickBooks at month-end. A direct API integration (auto-sync invoices, auto-match payments) is the most-requested feature on our wishlist but we haven't started.

    Gate: Will start when 10+ paying tenants name it as their #1 ask

  2. Native RFID kit tracking

    The owner mobile PWA uses BarcodeDetector (with @zxing/library fallback) for barcode + QR scanning, which covers what most plant + tool + party yards need. Native RFID with antenna hardware integration is what AV/events shops on Rentman use today.

    Gate: Will start when an AV-vertical tenant signs Pro tier

  3. Online customer booking portal (renter-facing)

    Today renters interact with YardGuild only via the magic-link waiver flow. A full renter-facing booking portal (browse availability, pick dates, pay deposit) would round out the self-serve story. Booqable does this well and it's a real reason some operators stay on them.

    Gate: Considered. We'd ship this if multiple operators tell us they're switching FROM us because we don't have it.

  4. Mobile-app dispatch + route optimization

    Heavy-equipment yards delivering 30+ daily drops with truck routing — what Point of Rental Elite does. We don't intend to compete on this. If you need it, PoR is engineered for it and we're not.

    Gate: Out of scope — not on the roadmap

How we prioritise

Want to shape what ships next?

Start a 30-day free trial and email hello@yardguild.com with your #1 ask. Paying tenants get a real vote in the queue.