google sheets + forgenow in beta

Your Google Sheet, behind a tool clients can see.

Half of every agency's operations lives in Google Sheets - the client tracker, the project pipeline, the timesheet, the rate card. The friction is that a sheet is built for your team, not your clients. Forge connects directly: each row becomes a record, each column a field, and the data renders inside a branded portal or status page on your domain. The team keeps editing the sheet they know; the client sees a finished, branded tool.

no code · we run the infrastructure · flat monthly pricing
the bottom line

Sheets run your operations. Forge turns them into what your clients see.

what you can build

Tools backed by a Google Sheet

how it works

Three steps to connect Sheets

Authorize Google

One-click OAuth from your Forge dashboard. We only read the sheets you authorize.

Pick the sheet(s)

Map columns to fields - which Forge tool reads from which sheet, and how often it refreshes.

Tool goes live

We build the portal or status page shaped to your sheet's structure - on your brand, hosted by us.

with vs without forge

Sheets alone vs Sheets + Forge

ForgeGoogle Sheets alone
Who sees itEach client sees their own branded viewAnyone with the share link - of the whole sheet
BrandingYour logo, colors, custom domainGoogle Sheets - their brand throughout
What's visibleOnly the rows / columns the client should seeWhole sheet (unless you build views or filter)
Polish for clientsA clean, designed toolA spreadsheet - even with conditional formatting
Setup & hostingWe build, brand, host and update itYou share, link and hope nobody breaks it
the bigger idea

Keep the sheet your team already uses

The most under-rated stack a small agency can run is 'Google Sheets for ops, Forge for the client-facing layer'. Sheets are free, infinitely flexible, and the team already knows how to edit them. Forge sits on top: same data, branded experience, on your domain. No double-entry, no migration, no spreadsheet-to-database project.

When the sheet structure evolves, Forge adapts - or we update the tool to fit. The whole point is that the spreadsheet stays the source of truth and your client sees a tool that looks nothing like one.

questions

Frequently asked questions

How does Forge connect to Google Sheets?

Via official Google OAuth - one click from your Forge dashboard. We only read the sheets you authorize, with read-only or read/write scope depending on what your tool needs. The connection can be revoked at any time.

Will my team still edit the sheet?

Yes - that's the whole point. The team keeps living in the sheet they know. Forge reads from it and renders the client-facing tool. No double-entry, no parallel system.

How often does the data refresh?

Configurable - typically near-real-time. You can set faster refresh for high-traffic tools (status pages) and slower for low-change data (rate cards, brand assets).

Can clients only see their own rows?

Yes. Each Forge tool is filtered to the rows you specify (typically by a client-id column) and rendered on its own URL - so each client only ever sees their own data.

What if I want a real database later?

Forge can move the data into our managed Postgres backend when you're ready - no migration project on your side. The transition is invisible to the client.

free templates

Start from a free template

Grab the static version now, or build the live, hosted tool with Forge.

go deeper

Guides & playbooks

In-depth guides on getting the most from AI and internal tools in your agency.

also worth a look

Compare, learn, decide.

design. build. iterate.

Keep your sheet. Show your clients a tool that looks like you.