Sula

Describe it once.
It updates itself.

Sula turns a sentence into a dashboard that keeps itself current — reading only the mail your views describe, citing every value it writes, and telling you when it isn’t sure.

Built for founders · in private testing

SulaRaise

Refreshes twice a day

Aperture Capital has gone quiet — nine days since they last replied, the longest of any live conversation.

Live conversations

£4.5M

Soft-circled

Pipeline

Investor	Stage	Last contact	Waiting on
Aperture Capital	Partner meeting	9 days ago	Them
Northgate Ventures	Diligence	4 days ago	You
Halden Partners	First call	6 days ago	You
Marrow Fund	Passed	3 weeks ago	—

Show all 9

Two investors are waiting on you, and one has gone quiet.

2Waiting on you
6Live
1Passed

Every investor I’m talking to, what stage we’re at, and who owes who a reply.

A live illustration of the real loop, built from the app’s own components. Nothing shown here is a capability Sula doesn’t have.

Reads Gmail and Calendar
Never writes, ever
Refreshes on a schedule
Every value cited

Who it is for

You are the integration layer.

The raise, the pipeline, the hiring loop — every system of record you have is really a spreadsheet you update by hand after reading your email. Founders have the most inputs and the least time, which is why they are the people we built for first.

“Every investor I’m talking to and who owes who a reply.”

The raise

Stage, last contact and whose court the ball is in — kept current from the thread itself, not from your memory of it.

“Everyone I’m interviewing and where each one is.”

The hire

Recruiter mail and calendar invites converge into one pipeline, so a candidate never goes quiet without you noticing.

“The design partners I’m onboarding and what each is stuck on.”

The customers

Blockers surface as they are mentioned, and repeat blockers surface as a pattern worth fixing this week.

It has no idea what a founder is. There is no investor feature inside Sula and no hiring template — one engine turns a described column into a sourced value, and it has never heard of a term sheet. Point it anywhere.

Flat hunt
Freelance invoices
PhD applications
House renovation
Visa paperwork

What it builds

A table is only one of the answers.

The planner picks the shape from what you asked for. A pipeline wants rows; a week wants a calendar; “what changed” wants a timeline. You never choose a widget type — you just say the thing.

Table

Rows keyed to real things

List

A compact single column

Timeline

What happened, in order

Calendar

Anything date-shaped

Brief

Prose, not bullets

Alert

The one thing that moved

The hard part

Anything can write you a table.
The question is whether you can trust it.

It can only read

Sula connects to Gmail and Google Calendar, and only ever reads. The access Google grants it cannot send, reply, delete, archive or label anything. Compromised tomorrow, the worst anyone could do with it is read what you can already read.

Every value is sourced

Each cell points back at the message it came from. Nothing changes without a citation, everything automated can be undone, and the log of what changed is yours to read.

It reads what you asked for

Sula does not ingest your inbox. It searches for what your views describe and opens the threads that match — a view about flats opens mail about flats.

The rule underneath all three: when Sula is uncertain, the failure is stale, never wrong. A value it cannot source is dropped rather than guessed, and a row it cannot confidently merge stays a visible duplicate rather than a silent one.

How it stays current

You describe it

One sentence, in your own words. Sula plans the columns and decides which of them come from your mail, your calendar, or the open web.

It finds the evidence

It searches your connected accounts for what the view describes, opens only the matching threads, and turns them into rows keyed to real things.

It refreshes on its own

On a schedule, it looks only at what has changed since last time. Where nothing changed, it costs nothing and touches nothing.

It tells you what moved

Changed values flip in place, each one carrying the message that caused it. Every automated change stays reversible.

Every morning

One moment of focus, not a feed.

Sula writes you a short brief on what actually needs you today. It is written as prose, because a list of eleven bullets is a way of refusing to decide what matters.

Tuesday

Daily brief

Northgate moved to a term sheet overnight — the paperwork landed at 23:40 and it is the only thing on today that can’t wait until tomorrow.

Aperture have been sitting on your data room for nine days now, which is the longest any live conversation has gone quiet. Halden asked a question on the 4th that never got an answer.

One focus: reply to Halden before the 2pm block, while the Northgate news is still fresh enough to mention.

Drawn from 4 threads and 2 calendar events · every claim traceable