An independent studio
3rd From The Sun
3fts is short for that. One small, independent studio, working on artificial-intelligence software and tools.
This is not a product page, because there is no product here to show. It is a description of the studio: how it builds, what it measures, and what it refuses to claim.
Every sentence below is either a fact about the studio or a statement of how it works. Nothing on this page is a promise about something you cannot see yet.
The studio
One studio, no layers, no outside funding
The studio builds artificial-intelligence software and tools. It is not an agency and not a platform company: it works on its own problems, at its own pace, and answers for the result.
It has taken no outside funding. That is a constraint as much as a choice — the work moves slower than it could, and every decision stays reversible by the people who made it.
Being small is the method, not the mood. A studio with no layers finds out that something is wrong earlier, because the person who built it is also the person who has to say so.
Method
How the work actually goes
The method is not clever. It is mostly a refusal to skip the boring part of the job.
Write the problem down first
Every build starts as a short written brief: what the problem is, what a good outcome looks like, what would count as failure, and what is out of scope. Prose is far cheaper to fix than code.
Build the smallest real thing
The first version is narrow on purpose and meets real inputs early. A prototype that only works on clean, tidy examples is a demonstration, and demonstrations do not survive contact with anything real.
Choose the measurement first
How the result will be judged is decided before the build, not after it. A measurement chosen afterwards is a justification, not evidence.
State the limits in the same breath
Anything written about a system carries what that system cannot do, in the same document and the same voice as what it can.
Make failures loud
A fault that is quietly absorbed is the most expensive kind, because nobody learns from it. Systems are built to say what went wrong and where, rather than to keep going and hope.
Keep the surface small
Every feature is something that must later be explained, tested and maintained. Scope is cut before it is built, not after a deadline has already been missed.
Principles
What we will not do
A principle is only worth writing down if keeping it costs something. These cost flexibility, and they are kept anyway.
- We will not call something finished because it runs. It is finished when it has been tested against the case it is for, rather than the case that flatters it.
- We will not publish a number we cannot reproduce. If nobody else can measure it again, it is an anecdote.
- We will not treat a limit as an afterthought. Whatever is said about a system carries what it cannot do, in the same place and at the same volume.
- We will not collect data a feature does not need. Where a design can keep someone’s information on their own machine, that is where it belongs.
- We will not sell, rent or trade personal data — and we will not build something whose business only works if we do.
- We will not announce a date we cannot hold, or describe something as ready while it is still in pieces.
Capabilities
The kinds of work this studio is built for
The studio is early, so this is a description of its equipment rather than of a portfolio. Each of these is a discipline it works in, not a product it is selling.
- Applied AI
- Agent tooling
- Data and measurement
- Privacy-first engineering
- Product design
- Developer tools
- Evaluation
- Local-first software
Applied AI
Making a model do one specific thing well, then making it dependable: evaluation, failure handling, latency, cost, and knowing where the model should not be trusted at all.
Agent tooling
The unglamorous half of software that takes actions on its own: tool interfaces, permissions, review points, logging, and what happens when a step fails halfway through.
Data and measurement
Deciding what is worth measuring before anything is built, then building the instrumentation first, so the answer exists by the time someone asks the question.
Privacy-first engineering
Designing so the safest handling of someone’s data is also the default one: local where local is possible, encrypted where it travels, collected only where a feature genuinely needs it.
Product design
Interfaces that explain themselves, and decisions that can be defended in a single sentence. A feature that needs a paragraph of apology is the wrong feature.
Developer tools
Command-line and local-first tooling that starts quickly, works without a network, and sends data nowhere it does not have to go.
Working together
How an engagement runs
Short, written and unceremonious. The shape is the same whether the job is three weeks or three months.
A written brief
We start with a page, not a call: the problem, who it is for, what success looks like, and what is explicitly out of scope. If that page is unconvincing, nothing gets built — which is the cheapest possible place to fail.
A small, real build
The narrow version goes up early and meets real inputs, while it is still cheap to discover that the approach was wrong.
Measurements, then judgement
The agreed measurement is run and reported as it comes out, including when it comes out badly. A number that only ever appears when it is flattering is marketing.
A plain handover
The work arrives with its notes: what was built, how it is measured, what it depends on, and where it is weak. Nothing that requires tracking down a former contractor to understand.
Plainly
What is not on this page, and why
So that nobody has to guess at the studio’s intentions.
- Nothing here is offered. The studio’s work is unfinished, so there is no download, no account and no form to fill in on this page.
- No dates. When something is finished it will be shown — with its limits attached — rather than trailed in advance.
- No borrowed credibility. There are no customer counts, no testimonials and no logos here, because there is nothing of that kind to show yet.
- No third-party requests. This page loads no analytics, no hosted fonts and no external images, so it renders identically with the network switched off.
That makes this a short page for a company page, and it will stay short until there is something real to describe.
Write to the studio
Email is the whole front door. If you have a problem worth a written brief — or you want to know how the studio would approach one — put it in a message.
One person reads it, and the reply will be an actual answer rather than a form letter.