Drive, Docs and Sheets inside the client record

Find the right file, preview it, read the sheet and make permitted edits without leaving the client. Every save is checked against the document afterwards.

Get early access All featuresHow it works
app.roasfinity.com/operate/workspace
Workspace screen in the ROASfinity app, with test data

Floating cards and figures are examples on sample data, not a customer account.

1The proof

Every number comes with its receipt.

Sample data, fictional brand. This is how Workspace shows a figure: the value, where it came from, the formula behind it and when it was last updated.

WorkspaceSample data, fictional brand
Launch briefGoogle DocSource and formulaEdited by the strategistUpdatedsee source
Creative trackerGoogle SheetSource and formulaRead, 120 rowsUpdatedsee source
Save checkMatches the changeSource and formulaLoggedUpdatedsee source

Rule: every number shows its source, formula and update time. A missing source reads "not measured", never 0.

2See it move

Channels light up one by one.

Each connector starts read-only. Built ones light up here, planned ones stay dim until they exist.

6 of 9 channels connected read-only, the rest planned. Example of 9 channels: 6 have a built connector that goes live per account once the platform grants access, 3 are planned and not built. 14 connectors are built in all.
3Part of Operate

Workspace: what it does.

One of four areas of the product, sharing the same client record, roles and log.

01

Search where the client lives

Files are found by client, with previews and permissions respected.

Workspace in the app, with test data
02

Edits that are verified

After a write the document is read again to confirm it matches the change.

03

Conflict aware

Revisions and simultaneous edits are handled, not overwritten.

Works with

1 platform, read-only first

Connections start read-only. Writing is switched on per account, only after you grant the rights.

At a glance

Stated up front

things it does
3
steps start to finish
4
platform connections
1
limits stated
2
4The data path

How the data moves. Source to screen.

Lines draw as you scroll. Platforms on the left are read-only first, Workspace sits on the one client record, and each output keeps its receipt.

Google WorkspaceRead-only first
ROASfinityWorkspace
Search where the client lives
Edits that are verified
Conflict aware

Sources are read first, the numbers are stored once per client, and every output shows its source, formula and update time.

How the work moves in Operate

The same four moves apply to every module in this area.

  1. 1 CaptureFrom the work itselfTasks start from comments, results, approvals and requests.
  2. 2 AssignRoles and ownersOne owner per task, and clients only see what they should.
  3. 3 TrackStatus in one recordDue dates, SOP steps and approvals sit with the client record.
  4. 4 LogNothing is lostEvery change is written to a log that cannot be edited afterwards.
5The routine

How it works, step by step.

From first connection to the number a client sees.

  1. 1

    Authorise

    Google OAuth with the smallest scopes that work.

    Workspace app screen with test data
    Step 1Authoriseexample
  2. 2

    Find and preview

    Search Drive and open Docs and Sheets in context.

    Step 2Find and previewexample
  3. 3

    Edit

    Make a permitted change through the Docs and Sheets APIs.

    Workspace app screen with test data
    Step 3Editexample
  4. 4

    Verify

    The saved result is read back and logged.

    Step 4Verifyexample
6In use

Built for businesses like these. Example scenes.

Photos are stock images that show the kind of business this is built for. They are examples, not customers.

Examplea small team
Examplea cafe or local shop
Examplea small team
Examplea creator studio

Stock photos and example labels, not customers.

7In practice

Common mistakes, and a short checklist.

General practice for this kind of work, not a claim about any one tool.

Mistake

Sharing one login across clients

A shared login hides who changed what and makes access hard to remove. Give each person their own account and a role that matches their work.

Mistake

Old permissions left in place

People who leave or change roles often keep their access unless someone removes it. Review permissions on a fixed schedule and remove what nobody needs.

Mistake

No structure people can follow

If folders, names and client spaces are not consistent, people search instead of working. Agree on one structure and write it down for every new team member.

A short checklist

Your ticks stay in this browser only.

8Honest limits

What it will not claim, and what it works with.

What it will not claim

  • It works within the permissions each person has in Google.
  • Complex formatting in Docs may need to be finished in Docs itself.

Works with

Connections are read-only first and go live only after the platform access is approved.

Google Workspace

Built: the connector exists in the product and goes live per account once access is granted. Planned: not built yet.

Used instead of

No single tool replaces this module; it connects work that is usually split across several.

10FAQ

Questions about workspace.

Which Google scopes are used?

The minimum needed for search, preview and the specific edits you allow.

Is document text sent to AI models?

Only relevant excerpts are selected after permissions are checked, and outputs show their sources.

Can it edit any file type?

Docs and Sheets are supported for edits. Other files are found and previewed.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Get early access How we plan to price it