Prototype

Welcome to GoldShoes

Your agency already knows everything.
GoldShoes puts it in one place.

Connect the tools you already use, or start fresh in minutes.

  • Asana
  • ClickUp
  • monday.com
  • Harvest
  • Clockify
  • Google Drive
  • Slack
  • QuickBooks
  • Dropbox
  • Microsoft Teams
  • Xero
  • HubSpot

Start in a few minutes.

Prototype sign-in — no account or connection is created.

“Was that file in email, Slack, Drive, or Dropbox?”
— nobody, after GoldShoes.
One source of truth for your agency — and, if you dare, your clients.
Channel-agnostic memory for your human and agentic teams.
01The problem

Nobody owns the truth about the client relationship.

Agencies run clients across eight to ten disconnected tools. There is no canonical source of client state—and the portal the client actually sees is the most rigid part of the stack.

8–10 disconnected tools

Payments, signature, proposals, email, CRM, project management, and file storage all hold a different piece of the relationship.

No canonical client state

Ask where an engagement actually stands and the answer lives in someone’s head—or four browser tabs.

Portals are rigid

Incumbent portals ship one layout, one brand posture, and one workflow. Agencies bend their process to the software.

Customization is shallow

A logo slot and an accent color are not white-label. The client still knows whose product they’re logging into.

02The shift

The frontend stopped being the hard part.

AI made customization trivial

Vibe coding turned a six-week portal redesign into an afternoon. Surface-level differentiation is now cheap.

Agencies want the surface

They have opinions about every pixel their client sees, and now they have the means to act on them.

They will not rebuild the plumbing

State machines, permissions, audit trails, and integration reliability are nobody’s idea of a fun sprint.

When the frontend becomes free, value migrates to the layer nobody wants to rebuild. That layer is client state.

One operating truth

Tools should be replaceable; operational memory should not.

Interfaces change. Teams change. The work still needs a durable place for decisions, commitments, context, and history—without making every person work from the same screen.

Day 1

Current work

Year 1

Patterns + benchmarks

Year 10

Institutional memory

First answers

The questions agencies need answered.

  1. 1Who needs to get invoices?
  2. 2Which clients are the most profitable?
  3. 3Where does time go missing?
  4. 4Is this a healthy account?
  5. 5Do we have capacity?
  6. 6What needs approval?
  7. 7Are communications on track?

GoldShoes Review

Ideas for independent agencies

Issue 01
The systems issue

All Agency Software Should Be HeadlessEven If Your Agency Isn’t Technical

The cover story

Headless simply means the underlying truth is separate from the interface used to see or change it. Creative, account, media, finance, and clients can each use a view suited to their work without creating five conflicting versions of reality.

One operating truth. Any interface.

Creative
Account
Media
Finance
Client
Rules
Canonical truth

Client services begin where your CRM ends.

Slack
Email
Asana
Clockify
Drive
Calendar
One holistic agency view

Game changer.

Your whole agency.

The agency control plane that connects the tools you already use and gives you one trusted view of clients, commitments, profitability, capacity, billing readiness, and institutional knowledge.

Headless Client OS.

A hardened kernel for the client relationship, with a beautiful, fully replaceable surface attached.

Backend — the kernel

State machine

Engagements as explicit, inspectable states—not a status column.

Permissions

Client, collaborator, contractor, and internal scopes, clearly enforced.

Audit log

Every transition, approval, and payment event stays queryable.

Integrations

Connectors write into the kernel, not around it.

Frontend — the surface

Fully customizable portal

A real white-label surface—the agency’s brand, end to end.

Production-ready themes

A polished, zero-effort path to launch.

Replaceable views

Project boards, reports, assistants, and approvals can evolve independently.

Ship on day one with a premium theme. Replace it entirely by day thirty. Same kernel either way.

Trust is a product surface.

Every useful answer should carry enough context to be checked, corrected, and trusted.

01

Provenance

Show where every number and claim came from.

02

Permissions

Least privilege, with explicit elevation.

03

History

Effective-dated terms and replayable changes.

04

Corrections

Retries, revocations, deletions, and conflicts stay visible.

The interface is replaceable.
Your agency history is not.

Today’s work becomes tomorrow’s patterns, benchmarks, and institutional memory.

Delivery
Review
Decision
Production
Dependency
Constraint
Week 1
Week 2
Week 3