Start a pilot
Eight weeks, priced up front.
An eight-week design-partner pilot at the list price - $40 a seat a month, invoiced for the seats you use. We set up your team's workspace on the call - and if you run an agent, its key and its first approved proposal too.
Opens your mail app · support@aurumtechnologyltd.com · Invoiced, not charged to a card
Start a pilotWhat happens
A working loop on the first call.
The call
About an hour
We create your workspace, add your people, and put your first project in it. If you run an agent, we mint its key, point it at the endpoint, and put its first proposal in front of you - you approve it, and that is the whole loop, end to end, before the call is over.
Weeks one and two
Your team, your work
You run it against work that actually matters - yours, your team's, and your agent's if you have one - and tell us where the shape is wrong. What is small and right gets fixed inside that fortnight, and what is not gets said out loud rather than promised.
Weeks three to eight
The way work lands
You use it as the place the team's work lives, and the place your agents' output arrives. We answer email. At the end you decide whether it stays, and nothing about that decision renews itself quietly.
What you get
Set up, in writing.
- Your workspace and your people, set up on the call - and if you run an agent, its key and its first approved proposal too.
- The async contract in writing, including what happens when nobody answers, for any agent you connect.
- Email support from the person who builds it.
- Every verdict recorded and attributed, with the trail exportable to CSV from the desktop app if it has to leave the building.
- The list price, held for the eight weeks.
What we ask
Three things, none of them a quote.
- Real work. Your team's actual projects, and if you run an agent, the one you actually run - a demo on invented work teaches neither of us anything.
- An honest account of where it does not fit, in the words you would use to a colleague.
- One call at the start and one at the end. Everything between them can be email.
The async contract
Plan for hours, not milliseconds.
This part applies when you connect an agent. A team that does not run one yet can skip it.
A verdict arrives when a human acts on it. That might be four minutes or it might be the next working day, and the loop is built for the second case. Your agent submits, gets a queued acknowledgement, and goes away. It polls later, from a fresh process if it likes, and picks up every verdict it has not seen.
Losing a connection, a process, or a whole day loses no work. A proposal nobody answers expires on a stated date rather than sitting open forever, and the expiry is itself a recorded verdict.
Written into the pilot, that is three commitments and one question. We commit that a verdict is not a request and a response, that your agent has to survive its own restart, and that nothing sits open indefinitely. The question is whether your integration can live with those. We would rather find out on the first call than in week six.
SUBMIT → queued, immediately
POLL → every verdict since your cursor
NO ANSWER → expires on a stated date, recorded
The endpoints, the cursor, and the failures that are quiet are written out in full on the connect page. Read it before the call if you are the one writing the client.
Plainly
What a pilot is not.
Not a discount. $40 a seat a month is the list price for a team workspace, and the pilot is deliberately invoiced at it, for the seats you actually use. A cheaper pilot would tell us something we cannot use.
Not a card checkout. We invoice you. Team seats are not sold by card, and no button on this site pretends otherwise.
Not a lock-in. Eight weeks, invoiced monthly. Tell us to stop and we stop.
Not a request for a testimonial. We will not ask for a quote, a logo, or a case study. If you offer one later, that is a decision for you to make then.
Why now
I built Aurum Life because I was tired of being the integration layer between five apps that didn't talk to each other. The bottleneck was never intelligence. It was context, and the willingness to let something act on it.
That second half turned out to be the hard one. Letting something act on your work means somebody has to be accountable for what it did, and a chat window is not a record of anything. This is the version of that I want to run myself.
We build it from Trinidad & Tobago, for everyone, not just the privileged few. It is early enough that what you say on the call changes what gets built, which is the honest reason to be a design partner rather than a customer.
One email, and a date in the diary.
Opens your mail app · support@aurumtechnologyltd.com