A finance team
Trimly
Month-end used to be a spreadsheet nobody else could open. Now the schedules, the next twelve months, and what's owed all sit on one screen the whole team can read.
Open TrimlyConcierge · £2,500 a month · 3 of 10 slots open
In 14 days, software does the job you were going to hire for.
Pick one job. The one that runs on a spreadsheet, two other tools and someone remembering to follow up. We document it, build it, and put it live on your own domain. Your team's total time: about four hours.
Live in 14 days. Or you don't pay for it.
Free. No slide deck. You leave knowing what we build first and the day it goes live.
Built and run by my team
trimly.app
A finance team's month-end. My team built it. My team runs it.
What you were about to spend instead
An ops coordinator on £30,000 does not cost you £30,000.
Salary £30,000. Employer National Insurance, 15% on everything above £5,000: £3,750. Pension at 3% of qualifying earnings: £713. That is £34,463 a year, or £2,872 a month, before you have paid a recruiter or covered a single holiday.
We are £2,500 a month. We start in 14 days. We do not resign.
The job I mean
You know which one.
Every business has one job that never got real software. It runs on messages, attachments and a spreadsheet. Here is how you spot it.
Before
Today.
The same details get typed three times.
One person knows the rules. They take a day off. The job stops.
You ask what is pending. Somebody has to go count.
A change means a developer, a quote and a month. So nothing changes.
After
Day 14.
Typed once. The rest fills itself in.
Anyone can run it. The steps are in the app, not in one head.
You open the screen. The answer is there.
You ask on Monday. You use it Friday.
Book a 30-minute call
That job costs you money every week. Nobody has time to fix it, because fixing it is a project.
What you get
Everything, one price.
One price, because splitting a build into phases and quotes is how these projects die halfway. Every line below lands in the same month, from the same team.
The job, written down (2 days)
We sit with the person who does it. Every step, every approval, every exception goes on paper. You pick what the first version covers.
Instead of: six weeks of meetings and a slide deck.
The app (live day 14)
Screens your team uses. Your information in one place. Logins, and each person sees only what they should.
Instead of: two freelancers and the gap between them.
It does the work
It sorts, checks, follows up and drafts. Your people just approve.
Instead of: the person who does all that by hand every morning.
ChatGPT can use it too
It looks things up in your app and does the jobs you approve. Same permissions you would give an employee. Nothing more.
Instead of: copying answers out of one tool and into another.
Your own web address
Your team opens it at your domain. Not a preview link with my name on it.
Instead of: hiring somebody to keep a server alive.
Changes every week (68 on the last one)
My team changed CK News 68 times in the six weeks after launch. The month buys those 68, not just the launch.
Instead of: a quote and a wait for every change.
You keep all of it
The app, the data and the code are yours. Ask on day 3 or day 300. My team moves it for you, free.
Instead of: finding out about the lock-in later.
All of it. £2,500 a month.Live in 14 days. Or you don't pay for it.
Book a 30-minute callFor the person you ask to check this
Its own Postgres database, sign-in and roles, server-side workflows, managed hosting with HTTPS, a REST API, and an MCP server so agents call approved actions instead of driving a browser. They can test all of it before you sign anything.
I set the price at £2,500 so it sits under one developer's salary. A number you can decide on your own, in one sitting.
Why this is different
A chatbot answers. This does the work.
Most software is a place to type. Somebody opens it, reads what came in, decides, and types. Nobody types, nothing moves. A chat box on the side does not change that.
Think of a new hire. They read the email. They check it against your records. They spot what is missing. They write the follow-up and hand it to you. That is what your app does, every day, without being asked.
And ChatGPT can do it too. It gets the same permissions you would give that hire, and nothing more. That is what the £2,500 buys.
Example: a new customerOne app. Three sets of hands.
YOUR TEAMDecides
Reads what the customer sent
Approves it
Starts the work
THE APPNobody asks it to
Files each document as it arrives
Writes the summary for whoever approves
Writes the follow-up when something is late
YOUR AI ASSISTANTSWhat you let it do
Look up a customer
Check which documents are missing
Start the work for them
ALL THREE WORK ONThe same informationThe same stepsThe same permissions
It gets the permissions you gave it and nothing more. The rules that cover an employee cover it too.
The price
£2,500 a month.
Everything on the list above. This is the price for the months my team is building. We agree what the first version does before any money moves.
Book a 30-minute call
Bring one job, the person who does it, and what it costs you today.
Month to month
Fifteen days notice to stop
Code and data go with you
Or pay for the year
$30,000.
Twelve months at $3,000 is $36,000. Pay up front and it is $30,000. You save $6,000, and your build starts first. Same notice. Same exit. I refund the months you don't use.
Afterwards
$1,500 a month.
Once the job stops changing and there is nothing left to build, the price drops. We keep it running and fix what breaks. You tell me when, not the other way round.
The promise
14 days. Or it is free.
On the call we agree what the first version does. I write the date down. My team misses it, you don't pay for it.
I promise it because it already happens. I sent the CK News plan on 12 July. The client opened a working app on 13 July.
How many I take
3 of 10 slots open.
My team builds ten at a time. Seven are running today. That is why I say no to websites and hourly work. That work pays. It would take a slot.
When ten are full, the next call goes on a waitlist. I tell you on the call, not after you pay.
BOOK THE CALL IF
The job already costs you.
It happens every week. One person owns it.
Waiting, re-typing and mistakes cost you money.
Your team can walk me through the steps.
You can decide how it works. No committee.
DO NOT BOOK IF
You want a list of features built.
The idea is vague. Nobody owns the result.
A website or an off-the-shelf tool already solves it.
You want developers by the hour, or a list of requests with no end.
It has to run on your own servers from day one.
Built and running
Open one and look.
Every screen below belongs to a real business using it today. Not a mockup. Click one and see.
An investment firm
CK News
Somebody had to read everything published about the fund managers they track. The app reads it instead, ranks what actually matters, and hands over a short list with every source.
Open CK News
A two-day conference
India Green Investment Forum
Sign-ups, tickets with QR codes, the agenda, the speakers and the sponsor packages, for a climate-finance forum in New Delhi.
Open India Green Investment ForumAnd this page
You're already looking at one.
This website runs on the same platform your app would. I put my own business on it before I ask for a month of yours.
CK News, counted
5Screens
14Kinds of record
11Jobs it does on its own
68Changes in six weeks
That is one app, six weeks after launch. The monthly price is what keeps a number like that going up.
The first 14 days
Call to launch.
You bring the job and the decisions. My team brings everything else.
DAY 0
We talk.
Thirty minutes. You walk me through the job. I write down what the first version does and the day it goes live.
DAYS 1–2
We write it down.
Steps, approvals and exceptions, on paper. You sign off before anybody builds anything.
DAYS 3–11
We build it.
Screens, logins, your data in one place, the work it does on its own, and the parts ChatGPT can use.
DAYS 12–14
Your team uses it.
Real work, and we fix what they hit. Then the part you are really paying for starts. We change it every week.
Your part is four hours
Two hours on days one and two, with the people who actually do the job, while we write down how it really runs. Two hours at the end, while your team uses it and tells us what is wrong.
That is the whole ask. We are not going to send you a requirements document to fill in. Doing it for you is the reason this costs what it costs.
Good first jobs
Start where it repeats.
Taking on a new customer
Their details, their documents, what is missing, the approval, and the handoff to the team who does the work.
Keeping customers updated
One place they see their files, their progress and what happens next. You stop sending the same update twice.
Quotes and approvals
A request comes in. It becomes a price. Someone approves it. The answer stays on the record.
The shared spreadsheet
The one that tracks who is doing what, and what is late. Retire it.
What is included
- You own the app. Your domain, your database.
- Changes after launch are included. One client sent 68 in six weeks.
- Cancel any time and keep the app.
- Your team's total time is four hours.
- Days 12 to 14 your team uses it and we fix what is wrong.
- Ten clients at a time.
What happens on the call
Thirty minutes. Three questions.
01
Which job, and who owns it.
Walk me through the steps. Show me where they go wrong and who patches them.
02
What it costs you now.
Waiting. Re-doing work. Extra staff. Customers lost to a slow reply. You have added it up. That number decides how much we build first.
03
What is live on day 14.
We cut the first version to something your team can use. I write the date down on the call.
Book a 30-minute call
No slide deck. You get what we agreed, in writing.
Book the call
Pick a time.
Thirty minutes on Google Meet. The invite comes from Cal.com. Check spam if it is not there in a minute.
Questions, answered.
What is the 14-day promise?
On the call we agree what the first version does. I write the date down. My team misses it, you don't pay for it.
What does £2,500 a month cover?
One app. Writing down how the job works. Building it. Putting it live at your web address. Running it. Changing it every week after that. Before we start I write down what the first version does, and which outside services bill you on their own.
Why only ten clients?
My own team does the building. Ten at a time is the limit. Seven are running today. That is why I say no to websites and hourly work. That work pays. It would take a slot. When ten are full, the next call goes on a waitlist. I tell you on the call, not after you pay.
We already have software. Why would we need this?
Most software only holds what somebody types. This one does the part of the job it can do alone. It sorts what comes in. It spots what is missing. It follows up on what is late. It writes the first draft and hands it to a person. If your software already does that, you don't need me.
Is this a demo, or can we run the business on it?
You run the business on it. Your team signs in. Each person sees only what they should. The data sits in a real database that is yours. For whoever checks these things: Postgres, HTTPS, managed hosting, a REST API and an MCP server.
Do we own it?
Yes. The app, the data and the web address are yours. So is the code. Ask on day 3 or day 300, not just on the way out.
Do we pay £2,500 forever?
No. £2,500 is the price for the months my team is building. Once the job stops changing and there is nothing left to build, it drops to $1,500. We keep it running and fix what breaks. You tell me when to switch. Want it to grow again? We agree the work and go back to the build price.
What if we want to stop?
Tell me fifteen days before the end of a month. No minimum term. No exit fee. You take the code and the data. My team helps you move it wherever you want. That takes time and I don't charge for it.
Can it work with the tools we already use?
We check each one before we start. If your tool can connect, we test it on the call or right after. I don't promise a connection I have not tested.
Who should not book?
Anyone who wants a website, developers by the hour, or a list of requests with no end. Anyone whose idea has no owner inside the business yet.
A note from Pragyan
Orbit is the tool. This is the work.
I built Orbit so people can build their own apps without me. Most of this website is about that, and the first app is free.
This page is the opposite. It's for the owner who has a job worth real money and no interest in learning a tool to fix it.
I set the price at £2,500 a month and I capped it at ten clients. Both cost me money. The cap is the expensive one: it means I say no to brochure websites and hourly work, and that work pays. I say no because it would take a slot from an app my team can point at afterwards.
My team and I built Trimly around a finance team's month-end and CK News around what an investor has to read every morning. The two have nothing in common. Bring yours. You already know what it's costing you. On the call, tell me the number.
Pragyan · Founder, Orbit
That job costs you this week. And next week. And the one after.
Pick the job. I will build it in 14 days.
£2,500 a month · 14 days or it is free · 3 of 10 slots open.
£2,500 a month3 of 10 slots open
Book a call