live database · retrieval you can read
You want someone who will write the playbook and run it in-market. The playbook's below. This page is it running.
Rees Calder. Application for Strategic Partner Manager. Every claim on this page is a row in a Supabase database. Ask it anything.
highlights
50+ wins, $25m+ lifetime partner and client value
$40m GMV platform, Head of Product & Partnerships
$200m global agency, BD & Strategy Director
Raspberry Pi, Bethesda technical and community partnerships, owned end to end
£0 → £100k as founder of Levity, my own AI & marketing business
Series A, +30% DAU from one challenger insurtech repositioning
1,000 → 20,000 MAUs in 12 months, on a nascent platform
24k+ memories in a bespoke agent memory system, built on Supabase
Thingiverse CMO of the world's largest open-hardware community
Or skip the PDF and ask the database directly.
demo
Interview my agent's memory
Each question is embedded, run through the search_memories() hybrid recall function on this Supabase project, and answered from only what comes back. The retrieved memories render below every answer.
83 memories in this site's corpus · Kern's own brain holds 24,980 (28 July 2026)
> Why should Supabase hire Rees?
Supabase should hire Rees because he embodies their core thesis that agents are the new users of databases. He has direct experience running his own AI operating system, Kern, on a Supabase Postgres project since April 2026. This practical application demonstrates his deep understanding of the platform. Rees has a proven track record of building and automating systems, as shown by his agency, Levity, which operates independently of his daily oversight. He has documented product friction with actionable solutions, showcasing his commitment to continuous improvement. His desire for high ownership and a technical team aligns perfectly with Supabase's culture. Rees is not just applying from the outside; he is already integrated into the Supabase ecosystem, having built multiple projects on it. His experience and vision make him a strong fit for the role.
embed 327ms · search_memories() 346ms · gpt-4o-mini 3.0s · total 3.7s
pre-run through this exact pipeline and shipped with the page · your questions run live
receipts · 6 memories retrieved via search_memories() · top similarity 0.703
ranked by hybrid search (RRF) · cosine similarity shown
Rees can start immediately. He runs his own business, so there is no notice period to serve, no gardening leave, and no handover to negotiate with an employer. If Supabase said yes tomorrow, he could be working the same week.
receipt 1Why Rees is applying to Supabase, in his words: Supabase's core bet is that agents are the new users of databases, and he is not adjacent to that thesis, he is a live specimen of it. His agent's whole world is one Supabase Postgres project, and he keeps the receipts: an 18-item friction log, each entry traced to code and paired with a proposed product fix. Kaizen is not a value he read on the careers page; it is the habit that produced the log.
receipt 2Kern is Rees's personal AI OS, built on the Claude Agent SDK, that has run his actual working life continuously since 8 April 2026 on a single Supabase Postgres project: email, calendar, scheduling, project work, and long-term memory. It is not a demo. Rees depends on it daily and it works while he sleeps.
receipt 3What happens to Levity if Rees joins Supabase: it keeps running. The agency was deliberately built to be automated, with agent systems handling most of the delivery work, so it operates without his daily attention. It is proof of how he builds rather than a competing commitment, and it poses no conflict: Levity is a Supabase customer, not a competitor.
receipt 4Why Supabase specifically: Rees is not applying cold, he is applying from inside the product. Kern, the AI operating system that runs his working life, has lived on a single Supabase Postgres project since April 2026, and his wider account runs 11+ Supabase projects across client and personal builds. He open-sourced his agent memory system built on Supabase, documented his product friction as cases rather than complaints, and built this very pitch site on a Supabase backend. He wants to work on the platform he already builds everything on.
receipt 5What Rees wants from his next role: high ownership with little process, a technical team that ships, and a company where AI is the operating fabric rather than a feature announcement. The Supabase job description's line about 'writing the playbook and running it in-market' describes how he has worked for a decade, and the AI Builder partnerships focus sits exactly where he has spent the last two years building.
receipt 6portfolio
What I've done and what I'm doing
Since 2012, across platforms, marketplaces, and agencies. Three shelves: what I've shipped, the partnerships I've built, and the pipeline I've sourced.
Mostly open-source and developer-community partners, which is the same room this role works in.
Raspberry PiWorked directly with founder Eben Upton
Deepened Raspberry Pi's integration into the open hardware and 3D printing communities.
Open Source Hardware AssociationLed the OSHWA x Thingiverse partnership
Connected the Open Source Hardware Association with the world's largest 3D printing community.
Eagle LabsTook MyMiniFactory into the Eagle Labs network
Brought CAD and 3D printing to more people through Barclays' national maker spaces.
at the tree, 2017–2020Hardware and software built for one campaign
Agency client work at the tree: physical and digital builds in one marketing programme, shipped together.
BBC micro:bitCollaborator on the micro:bit programme
Helped put programmable hardware in the hands of a generation of UK school kids.
✓ = queryable. Click any tick to run that claim against the live database, receipts and all.
playbook
A draft of the artifact the job description says I'll write.
I work best with a lot of ownership and little process, which is what the JD describes. Give me a target and I'll move fast and write the decisions down as I go. So rather than tell you I'd write the AI Builders partner playbook, I had a go at it: six partners scored, a four-tier ladder, an answer to Neon's Agent Plan, the free-tier arithmetic, and a dated first 90 days.
Draft 0.1 · July 2026
Written as part of an application for Strategic Partner Manager at Supabase. Every claim is either cited to a public source or stored in the Postgres database behind this site. Ask the chat to interrogate any of it.
supabase native
I run my whole working life on Supabase.
kern · personal AI OS · supabase-native
My agent has run my working life on one Supabase Postgres project since 8 April 2026. Press GO and it will show you the receipts.
$ status: sealed · 10 figures inside
next step
That's the pitch.
The playbook is drafted, the numbers are on the cards above, and the Supabase knowledge comes from running my own production on it since April and writing down everything that broke. Every claim here is a row in a database you can query yourself. Let's chat.
I'm in Cape Town, UTC+2: a full working-day overlap with EMEA and a workable overlap with US mornings. I ran Thingiverse from here for a US-centred company, so I know the setup works. Pick any slot that suits your timezone.
reescalder@gmail.com