PeopleCount Build

What you can’t buy off-the-shelf, we build.

Custom marketing sites — editable by your team, hosted on your domain. Custom modules that live natively inside Platforms. All of it built by the same team that ships the product.

Start a scoped conversation
What Build delivers

Two kinds of custom work.

Marketing sites

Hosted on your domain, yours to own. Editable content fields are scoped during the build, so your team can update the parts that change. Most Build engagements are here: opinionated, accessibility-first sites.

Custom Platforms modules

Native to your account, sharing the same login, data, and mobile app as every other module. What you build fits the system you already run on.

Case study

Freedom Tires is a mobile tire sales and service franchise. Each location runs its own day-to-day — dispatch, service, billing — while sharing training, playbooks, and reference data across the network.

They needed two things no off-the-shelf SaaS had: a public marketing site to drive inbound leads, and an operating system that could serve both the franchisor (full admin) and the franchisees (a curated portal). Plus somewhere to hold the reference data their technicians actually need in the field — 760 lugnut torque specs, indexed by make, model, and year.

Build delivered

  • A public marketing site at freedom.tires — self-hosted by Freedom Tires, with editable content fields configured for their team.
  • A PeopleCount account with Core, Launchpad, Documents, Portal, Playbooks, Data Tables, Project Management, Scheduling, and Custom Fields — all turned on and configured for the franchise model.
  • A custom Data Table — Lugnut Torque Specs — with 760 entries indexed by make, model, and year.
  • A franchisee portal view tuned to what a single location sees: training, documents, reference data, and Riley, our AI assistant searching over all of it.
  • Branded throughout — logo, colors, copy — native to Platforms, not a skin on top of it.
freedom.tires
Freedom Tires marketing site homepage.
The public face — user-editable by the Freedom Tires team, hosted on their domain.
Franchisor admin
Freedom Tires admin dashboard, with Next Steps setup checklist and a grid of enabled Platforms modules.
Kenny’s command center — module status, setup checklist, admin controls.
Franchisee portal
Freedom Tires franchisee portal view with training units, lugnut torque specs data table, documents, and an Ask Riley panel.
A franchisee’s view — their training, their reference data, Riley over the docs.

Kenny’s testimonial quote will land here before launch. Two or three sentences in Kenny’s voice about what Build delivered for Freedom Tires.

— Kenny Gingras, Owner, Freedom Tires
How an engagement works

Five phases.

  1. Intake

    You send the request form with a rough scope and a budget band. We read every one.

  2. Scoped proposal

    If the shape makes sense, we come back with a written scope, a fixed or estimated quote, and a proposed timeline. If it doesn’t, we say so early.

  3. Build

    We build in the open. Regular check-ins, in-progress previews, no surprises at delivery.

  4. Ship

    You launch. Custom marketing sites go to your hosting (you own the IP); custom Platforms modules go live in your account (we host, you use).

  5. Maintain

    We charge an hourly rate for ongoing maintenance after ship. Net-new scope gets its own proposal.

Ownership and hosting

Who owns what, plainly.

Ownership is the question every serious custom-software buyer asks before signing. Our answer is the short version of what ends up in the contract:

If you host it, you own it.

Custom marketing sites — like Freedom Tires’ — run under your domain, on your hosting. Editable content fields are scoped during the build, so your team can update the parts that change. You retain IP.

If we host it, we retain IP.

Custom modules live inside your PeopleCount account, sharing the same login, data, and mobile app as everything else you’ve turned on. PeopleCount retains IP; you get perpetual use for your business. Your account keeps running on what we built.

A specific problem, a specific scope. Let’s see if Build is the right fit.

Start a scoped conversation