Blankdesk is the do-it-all tool for builders and teams who work in Claude, ChatGPT, or any other AI client. Any internal tool you need: a CRM, a dashboard, a task board, a form, a hiring tracker, and more. Describe it, ship it, and your team is using it in minutes.
Build us a CRM for founder-led sales: companies, contacts, deals, every call.
Here's what I'd set up. Nothing has changed yet.
organizationspeopledealsactivitiespipeline_snapshotsClosed-won deals need an amount and a close date.
Apply it?
Apply it.
Applied: five tables, two rules.
Ready for your HubSpot contacts? I can read them through the HubSpot connector and show you the preview first.
Hiring board: candidates by stage, a Flag button per card, a form for referrals.
Built and saved as hiring_board, so anyone on the team can open it:
Add a Reject button that asks for a reason.
Version 2: Reject on every card, the reason in the preview you confirm.
Show the launch board.
Six tasks. Drag a card to move it, right here:
Each move is recorded, and the board tells me what changed.
Log my call with Brightline from today's notes, follow-up Friday.
They want SSO before signing, and Priya Nair is the new champion. I'd record:
Commit?
Do it.
Committed. The summary is on the deal; Friday's follow-up is set.
Give Dana the hiring pipeline, not the fundraising tables.
Dana's access after the change:
Dana's own database login carries exactly this access.
Apply?
Apply.
Applied, and recorded in the history.
A pipeline you drag deals across, a dashboard, a form, a calendar. Describe it and your assistant writes the board; Blankdesk runs it in the chat and previews every change before it lands.
Make me a pipeline board I can drag deals across, with a flag on anything that's stalled.
Here's your board, saved as pipeline so the whole team can open it. Drag a card to move it.
The board told me what moved. Want a follow-up set on Umbrella's renewal?
Describe the screen and your assistant writes it: layout, controls, chart. Want a Reject button or a total on top? Ask; it's version 2.
Every button and drag ends in Blankdesk's own preview, with a Confirm only you press. The board's code can't commit anything itself.
A saved board opens for anyone you've given access, with their permissions, and keeps every version. No dashboard, no login, nothing at a URL.
Boards render in the Claude web and desktop apps today. In apps we haven't verified yet, your assistant gets the same data and shows it as a table.
Vendors are putting AI inside their apps. Teams who live in Claude or ChatGPT go the other way: the assistant reads, writes, and reminds; the app is left as a database and a bill.
Blankdesk is the app built for inside the AI: your own database, with the rules, schedules, history, and boards a real tool needs, and none of the per-seat bills.
A handful of tables, a few rules the database enforces, a schedule or two, a board to work in. Your assistant sets each up from a prompt.
Instead of HubSpot, Attio, Close, or Pipedrive.
organizationspeopledealsactivitiespipeline_snapshotsInstead of Asana, Monday.com, or ClickUp, and for the non-engineering work that ends up in Jira or Linear. Engineering work tied to the repo stays where it is.
projectstaskstask_dependenciesstatus_updatesInstead of Visible, Foundersuite, or Folk.
organizationspeopleroundspipeline_itemscommitmentsactivitiesInstead of Ashby, Greenhouse, or Lever, for referral and sourced hiring.
rolespeopleapplicationsinterviewsscorecardsoffersInstead of Productboard, Canny, or Enterpret.
feedback_itemsfeature_requestsfeedback_linkscustomer_valuesInstead of Vendr, Zylo, Cledara, or the renewals spreadsheet nobody opens.
vendorscontractsspendbudgetsInstead of Airtable, Notion databases, Smartsheet, or a spreadsheet.
Hiring plans, headcount, OKRs, board action items, partners, equipment, a content calendar: real tables with enforced rules, previews, and a change history.
Product names are their owners' trademarks, used here only to describe what Blankdesk can stand in for. Blankdesk isn't affiliated with or endorsed by any of them.
For the reader who wants to know what's underneath the hood.
mcpA remote MCP server with OAuth sign-in. Any client that speaks MCP can connect, to one workspace.
Blankdesk is a remote MCP server with OAuth sign-in. Any client that speaks MCP can connect, and a connection is bound to exactly one workspace.
code modeThe assistant writes one small program per task instead of picking from hundreds of tools.
The assistant gets search, get_schema, execute, commit, and show, which only renders a board. Instead of a fine-grained tool per action, it writes a small JavaScript program that reads and changes data in one run. Far fewer tool descriptions in the context window, faster tool selection, and one approval point: commit.
sandboxGenerated code runs in an isolated Worker with no network, no credentials, and a guard on every query.
Each run gets an isolated Worker with no network, no environment variables, no credentials, and hard limits on how many queries it can run and how long it can take. Every query passes a statement guard that parses the SQL and blocks anything that would escape the transaction.
boardsA board's HTML runs in a frame with no network; every change goes through Blankdesk's own preview and Confirm.
A board's HTML, written by the assistant, runs in a frame of its own with no network and no reach into the page around it. All it can do is ask Blankdesk to preview an action the board declared. The preview and the Confirm button live in Blankdesk's own panel, outside the board's code, and the commit gets every check a commit gets.
postgresEvery workspace is its own Postgres database, and every member logs in as their own role.
Every workspace is its own Postgres database, and each member logs in as their own database role with only the access they've been given. The audit log is written by the database itself, so generated code can't forge or edit it.
previewsA preview runs the change and rolls it back; commit refuses if anything changed since.
A preview runs the change in a transaction, records every row it would touch, and rolls back. Commit runs it again and refuses if the rows or the schema changed since the preview.
migrationsA migration runs in a transaction, is diffed, rolled back, and applied only after approval.
A migration is proposed as SQL, run in a transaction, diffed against the current schema, rolled back, and applied only after approval. Migrations are schema-only; data changes go through previews.
schedulesSaved functions are versioned, and a schedule pins the version it runs, on cron.
Saved functions are versioned, and a schedule pins the version it runs. Scheduled runs execute as a separate automation role, on Cloudflare Workflows driven by cron.
exportStandard Postgres: ask, and you get a pg_dump. Bring your own Postgres is coming.
Standard Postgres with standard tooling: ask, and you get a pg_dump of your workspace with schema, data, and history. Bring your own Postgres is coming: point Blankdesk at a database you already run, and the same setup runs on it.
securityPermissions and membership are checked per request, never trusted from a token; credentials are encrypted at rest.
Permissions, owner status, and membership are checked per request on our side, never trusted from a token. Credentials are encrypted at rest. Every change runs a security test suite that covers the roles, the sandbox, the statement guard, and the audit log.
We're working out pricing with the first companies on board. Join the waitlist, tell us what you'd replace, and we'll talk it through with you directly.