Event
Office hours: bring the paragraph, leave with a plan
A standing hour with the people who build this.
By Sofia Marchetti · Field engineering · 10 June 2026 · 3 min read
Once a fortnight, an hour, with the people who actually build this. Bring the analysis your team keeps redoing and we will tell you honestly whether it is a good fit for an application — including when the answer is that it is not.
There is no deck. Nobody from a commercial team joins unless you ask for one. The stated purpose is to find out whether the thing you are describing is the shape of work this platform is good at, and the fastest way to establish that is to talk to somebody who has built several of them.
What to bring
One paragraph, written by whoever actually does the work.
Not a requirements document, not a process map, and preferably not a slide. A paragraph in the words your team already uses: what comes in, what has to happen to it, what "finished" means, what has to be explained rather than resolved, and who reads the answer. If you can write that in ten minutes, you have what you need for the session.
If you have a workbook, bring the workbook too — but the paragraph first. A spreadsheet handed over without a description gets read as a specification of its layout, and its layout is the least interesting thing about it.
How the hour usually goes
Four parts, and the last one is the one that makes the session worth booking.
- Is this an application at all — about twenty minutes. Some work is a query, some is a report, and some is a genuine analysis with a sequence and a set of rules. Only the third kind benefits.
- Where the inputs come from — about fifteen. This is where most of the real difficulty lives, and where an optimistic estimate usually turns into a realistic one.
- What it would meter — about ten. What a run of this would spend on storage, compute and model usage, honestly rather than reassuringly.
- When the answer is no — as long as it takes. We have told people not to buy this, in this session, more than once.
The three answers we give most often
"That is a query, not an application." If the work is one question against one dataset and the answer is a number, an application is a heavy way to get it. A well-written query in the tool you already own is the right answer, and we will say so.
"The hard part is the data, and we do not solve it." Where inputs arrive as email attachments from four different people at unpredictable times, the analysis is not the bottleneck. An application will run beautifully on the days somebody remembers to send the file.
"Yes, and the first fortnight is a fortnight." The genuine fits are the ones where a real sequence of rules is executed repeatedly by people who understand it. Those work well, and they still take two weeks of your analyst's attention to get right — spent correcting, not waiting.
Practicalities
An hour, video, no recording unless you ask for one. Bring as many people as you like, though the useful number is two: whoever does the work, and whoever would pay for it.
Nothing is signed in the session and nothing follows it automatically. If it turns into an engagement, that starts as a separate conversation with a scope and a price attached — conversion work is a services line, quoted per piece of work, and it is never bundled into a platform subscription.
If you would rather not talk to anybody yet, read the piece on describing an analysis first. Half the people who book this session arrive having already answered their own question, which is a good outcome and costs us nothing.
The figures in this piece — including the ones in the panels — are illustrative. They show what a result of this shape looks like, not a measurement of anything that happened.
Read next
Save your place
What happens next
Thank you. We will write once, when it's ready.