The finance back office, running inside a Google Sheet

Built by someone who ran the close

Most finance software is built by engineers who have never closed a month. Most people who have closed a month do not write software.

Dmitry Kuzinets is a CPA and former PwC auditor who spent sixteen years in SaaS and fintech finance, in controllership and FP&A, before building this. He works where there is an accounting problem and a systems problem at the same time.

You sign off on these numbers, so you get to inspect them

Derived figures are live formulas, not stored values. Click any one and walk it back to the source document. Where the software makes a judgment call, such as how to read an ambiguous contract term, that call is logged for a person to review.

When your auditor asks where a number came from, you show them. You do not reconstruct it.

Who it's for

Finance teams at SaaS and fintech companies between roughly $25M and $250M: the controller, the VP of Finance, and the CFO who signs off on a revenue number they did not build themselves.

Under ASC 606 the revenue arrangement lives in the signed contract, not the ledger. So someone opens each PDF, works out the performance obligations, allocates the transaction price, and maintains a monthly schedule by hand. It is manual, it belongs to one person, and nobody can trace it when the auditor asks.

Companies this size carry the audit and board-reporting obligations of a large company on a finance team sized for a small one. The conventional fix is replacing the ERP, which most of them cannot absorb while still closing the books every month.

What it does

Contract extraction. Connects to your ERP and CRM and reads signed contract PDFs to extract their ASC 606 revenue arrangements: the performance obligations and the transaction price allocation. Every extracted term stays linked to the page it came from.

Revenue and billing schedules. Builds both from the same contract and keeps them current as contracts are amended and renewed.

MRR and the bridge back to GAAP revenue. Produces MRR from the same contract data, plus a categorized bridge explaining why recognized revenue and MRR moved differently. As far as I could find, nothing else on the market ships that bridge.

Journal entries. Drafts the revenue and deferred revenue entries for a controller to review before anything is posted.

Close tracking. Tracks the month-end close with multi-level sign-offs.

Variance analysis. Drafts commentary that reads the documents behind a change, including invoices, contracts, and memos, not just transaction descriptions.

Statements, KPIs, and board decks. Built from the same live data, so the deck and the ledger cannot drift apart.

Integrations. Connects to your existing accounting system and CRM.

How it works

It runs on Google Cloud, with Vertex AI powering the contract extraction. It works inside Google Sheets as a Workspace add-on, currently being packaged for the Google Workspace Marketplace.

It connects to your accounting system and CRM over their APIs and writes its output into your own Workspace, sitting on top of the finance stack you already have rather than replacing your ERP.

Less like enterprise software, more like a very good spreadsheet that runs the close.

How you get it

SuiteCortex is licensed software, delivered inside your own Google Workspace and implemented by the person who built it. Scope is set by the number of entities and the volume of contracts under management.

Nobody self-installs revenue recognition, and you should not want to. A configuration mistake there does not announce itself: it sits in reported numbers until an auditor finds it two quarters later. So the implementation is done with you, against your contract structures, your chart of accounts, and your close calendar.

You are buying an outcome, not a system to learn. What you do get to inspect is every number it produces.

Every engagement starts with a scoping call, where I tell you what this would and would not fix for you. Some finance teams do not have a problem worth solving this way. If yours is one of them, you will hear that on the call rather than three months into an implementation.