Some work needs its own app. We build it with you.
General tools stop where your process starts. We learn the systems your
team already runs, build the app your work needs, and keep building it
with you.
Most of the value is in the details: which tab counts as live, and what the Monday report is really for.
Sit with the team
We join your channels and standups, read the trackers and threads, and learn the rules only your ops lead knows.
Build on the platform
Your app inherits connectors, chat, approvals, automations, and receipts. We build what is specific to you.
Keep your tools
If the team lives in Google Sheets, the sheet stays the sheet, syncing both ways.
Ship, then stay
A named engineer in your Slack, a weekly sync, and early access while it is being built.
What we build
The shape of a custom app.
Each one is an app the team works in, and an agent that knows the records behind it.
A CRM behind your sheets
Partners tracked across several spreadsheets. One search over all of them, and a line between partner and internal views.
Intake and triage
Requests arrive by email, form, and Slack. Each one filed, the reply drafted, the rest routed to a person.
The weekly report
Numbers from six sources, checked against last week, with the deck staged on your template.
Reconciliation
Invoices against the tracker against the bank export. Mismatches flagged with a reason.
Renewals and commitments
Contracts and rate cards across dozens of vendors. A reminder before a date passes.
Asset operations
Draft, review, approval, publishing. Ticking a box moves it on with its links intact.
A question desk
“How many are live this year, by region?” answered from the records, with the counting rule shown.
A review queue
Every outgoing deck or contract checked against your rules, with the failing rule named.
What a custom app is
A UI for the team, and an agent that knows the records.
Every custom app is two things at once. The team gets a plain interface: a
search, a grid, the views they asked for, and rules that stop a bad row
as it is typed. Friday gets the same records, with the rules written
down.
The apps are AI-native. The chat, the records, and the rules are one
system, so a question comes back with the number and the rule that
produced it.
Data stays where it belongs. A Google Sheet can stay the sheet, syncing both
ways, with the records and rules behind it.
VendorsCustom app · 84 vendors · 3 teams
New contract
north
Renews this quarterMarketingEngineeringTeam: any
VendorTeamRenewsTerms
Northwind PrintMarketingOct 14Rate card v3Current
Northstar MediaMarketingNov 2—Terms unconfirmed
North Fork StudioEngineering——Do not renew
Which contracts renew this quarter, by team?
11 contracts renew before December: 6 in Marketing, 3 in Engineering, 2 in Ops. Two have no confirmed terms yet and are flagged above.
How this was countedView renewals_q4 · a contract counts when its end date falls in the quarter and its status is not “do not renew”.
What every build gets.
One search across everythingEvery record, note, and decision in one place, including the ones you decided against.
Guardrails as rows are typedDuplicates, bad dates, and rate mistakes flagged with a reason, before money moves.
Two views of the same recordsPartners see their own work. The internal team sees everything, including what each partner negotiated.
Handoffs as triggersA status change moves the item on, and starts the automation that follows.
Answers with receiptsEvery number comes with the counting rule that produced it.
A morning digestA Slack message each day with what is waiting on whom.
The agreement
What you own.
A custom build should leave you less dependent on a vendor. The
agreement, in plain words.
Your data is yours. You own it, always, and can export it at any time to Sheets, CSV, JSON, or a full SQL dump.
Your app is yours too. The records, views, rules, and reports we build for you belong to you. The platform underneath is licensed, and platform improvements reach your app without breaking it.
Continuity, in writing. Escrow or handover terms, uptime and response commitments, and a documented transition if you ever leave.
Security you can review. Hosted on Google Cloud, encrypted in transit and at rest, with tenant isolation, role-based access, and single sign-on. We are working toward SOC 2 and will walk your security team through the details.
Two fees. A one-time build fee, then a platform fee that includes the team's compute budget.
Is this you?
Who this is for.
A good fit
Ops, marketing, and finance teams whose “system” is really a dozen trackers.
Teams coordinating several partners, agencies, or vendors on one program.
Money or commitments moving through spreadsheets, and a report nobody fully trusts.
A data team tired of answering the same questions with screenshots.
Probably not
If a general tool already fits, use it. Friday's own apps and connectors may be all you need.
If the manual path is faster, safer, or clearer, we will tell you, and we won't build something you won't use.
Bring the process that gives you the most trouble.
The first conversation is a working session on one of your workflows. If we cannot show something useful on your own data, we will say so.
