Website · Brand · Automation
Cars and Coffee Sac
A car community that already worked. We built the system underneath it.
The challenge
A community that outgrew its plumbing.
Most of the work on this page starts with a business that needs explaining to people. This one did not.
Cars and Coffee Sac runs a free monthly event in Sacramento with a real audience showing up and sponsors paying to be part of it. The name is known in the local scene. Nobody needed to be convinced it was worth attending.
What it did not have was anything underneath that. The site sat on a page builder that could do little more than display. Vendor and sponsor requests arrived through a basic form. Payments came in through whichever app someone happened to use, and got matched to bookings by hand, one screenshot at a time. Every new partner meant redrawing artwork from scratch.
So the job was not inventing a brand. The brand existed and people recognized it. The job was building the machinery a growing organization needs and does not get for free.
What we did
Built once, then reused.
01
Moved the site off the old builder.
A re-point rather than a transfer, so ownership of the domain never changed hands. Records rebuilt from scratch and cut over with no gap in service.
02
Rebuilt the site.
Built from scratch. Mobile first, a dark automotive palette, and the search and social tags set properly on every page.
03
Systematized the brand without touching the mark.
We did not design the logo. Cars and Coffee Sac already had one, and it was not ours to redo. What it did not have was rules. We locked the palette with computed contrast ratios, split it into text, fill, and large type roles, set four tiers of type, and delivered a Brand Board and a standalone usage guide the organization keeps. Capturing an identity that works is a different job from inventing one, and it is the job this needed.
04
Built a co-branding system instead of a co-branded graphic.
Fixed skeleton, one swappable partner slot. A new partner drops into artwork that already exists rather than triggering a redraw. This is the piece that makes everything after it repeatable.
05
Built the partner program as a template.
Not as a one-off. Adding another partner took one configuration entry and a rerun of the template.
06
Replaced the form and the screenshots.
Vendor and sponsorship requests now book and pay in the platform. Free membership runs on a signup form, a member tag, and a client portal. Forms, calendars, pipelines, workflows, tags, and a products catalog all live in one place, which means a booking is a record rather than a message somebody has to remember to act on.
07
The parts nobody sees.
Email sends authenticated from a subdomain rather than the root, deliberately, so the address the organization already uses was never touched. Every offer has its own consent field and its own self-describing field key, never shared between offers, so consent given for one thing is not quietly reused for another. Accessibility was a build requirement rather than a pass at the end. The legal pages are published, including the commercial terms the partner program runs on.
The takeaway
A community that welcomes everyone has to be able to grow without a redraw.
Where it landed
A community that can grow without redrawing anything.
The car scene tends to run on exclusivity. The right car, the right people, the right invitation. Cars and Coffee Sac runs the other way, and does it on purpose: all years, makes, and models, free, all ages, pets welcome, rotating venues, first Sunday of the month, 8 to 10am. The house rules are about respect for the venue, the cars, and each other. No burnouts, no loud revving, no reckless driving. The organization's own material says "Welcome home."
That is an identity, not a tagline, and it is the thing the system has to protect. A community that welcomes everyone has to be able to add a partner without a redraw, take a vendor booking without a screenshot, and sign up a member without a spreadsheet. Otherwise the welcome runs out at exactly the point where the organization gets big enough to need it.
What that looks like in practice:
- Vendor and sponsorship requests arrive as paid bookings rather than as a form submission somebody has to chase
- Adding a partner is a configuration entry, not a design project
- Membership signups create a tagged contact with portal access
- Email sends authenticated, from a subdomain that leaves the existing address alone
- Every consent is recorded per offer, against its own field key rather than a shared one
Outgrown your own plumbing?
If the thing you built works and the machinery around it does not, that is the work we like most.
Tell us about your business