Prefer to self-serve?
The four-question assessment covers the same logic and takes about three minutes, with no email required.
Start the assessmentBook a call
Thirty minutes. One workflow. A straight answer.
Tell us the process that costs you the most time or money. You leave the call with a lane — rent, extend or own — and the reasoning behind it in writing.
- Rent
- Extend
- Own
Session · Live
Free · Engineering lead
30
minutes
One workflow. A straight answer.
On the call
- 00′Name the costly workflow
- 10′Pressure-test rent / extend / own
- 25′Leave with the written view
Lane for this workflow
Settling…
Rent
Extend
Own
Output · Written view
Recommendation: Own
Reasoning for this workflow — why rent and extend were set aside, and what owning changes on the balance sheet.
- Length
- 30 minutes
- Cost
- Free
- You speak to
- Engineering lead
- Output
- Written view
Request a time
Agenda
How the half hour is spent.
0–5 min|Context
What the business does and where the pressure is right now.
5–20 min|One workflow
The steps, the systems, the exceptions, and the manual work in between.
20–28 min|The lane
Rent, extend or own — with the reasoning, a rough range and a sequence.
28–30 min|Next step
Either a written recommendation, or an honest 'nothing to do here'.
What it costs
Money, said plainly.
We publish ranges rather than making you sit through a discovery process to find out whether this is affordable.
Assess
Free
One call and a written lane recommendation on a single workflow.
Pilot
Fixed scope, five figures
One workflow built and put live in production, with a measured before and after.
Ongoing
Monthly capacity
A small senior team extending the system, cancellable, with ownership transferred as we go.
Ranges, not quotes. The exact number depends on how many workflows, integrations and users are involved — which is what the first call establishes.
Questions
What people ask before booking
If something is not answered here, ask it on the call — or email info@fxbytes.com.
- What happens on the call?
- You describe one workflow that frustrates you. We ask about the systems involved, who does the manual work, and what it costs when it goes wrong. Then we say whether it looks like rent, extend or own — including when the answer is to leave it alone.
- Is it really free, and is it a sales call?
- It is free and there is no obligation. You speak to an engineering lead, not an account manager, and you get a short written recommendation afterwards whether or not you engage us.
- We are a small business. Are we too small?
- No. Most first engagements are a single workflow for a team of 20 to 250 people. Small scope is an advantage — it is easier to measure and quicker to put live.
- What do we need to prepare?
- Nothing formal. A requirements document is not needed and often slows things down. Bring the name of the workflow and roughly how many hours a week it consumes.
- Who owns the software you build?
- You do. Source code, data and IP are yours, in your repositories and your cloud accounts, from the first commit.
- What does an engagement typically cost?
- A pilot on one workflow is normally a five-figure engagement, fixed in scope before it starts. Ongoing platform work is a monthly capacity arrangement. We give a range on the first call rather than after three meetings.
- How quickly does something go live?
- A first end-to-end path in production usually takes six to ten weeks from the point scope is agreed. If a workflow cannot show value in that window, we break it down further rather than starting a larger programme.
- What happens if we stop working together?
- Nothing breaks. The system already runs in your accounts on your repositories, with runbooks and documentation maintained as we go, so another team — or your own — can pick it up.