Way 01 · Figure It Out
A good question is a very good start.
We turn uncertainty into a decision you can act on.
What it is for
‘We enter the same details twice. Where should we start?’
‘Something has to change. Nobody knows yet what to build.’
‘Someone else built our website. Is it secure?’
‘Nobody quite knows who can reach what on our office network.’
What we do
Look first, then decide. Sometimes the answer is an Excel macro. Also fine.
Workflow (A workflow specifies what information goes in, what happens to it and who checks the result.) and problem discovery
We start where the work happens: the inbox, the spreadsheet only one person understands, the program somebody retypes everything into. Then we draw it out: who does what, with which document, in which program.
Technical feasibility and second opinions
Can it work at all, and does the plan on your desk do what it promises? We check before you spend money on it. The security checks belong here too: they show what is exposed.
Architecture and build-or-buy decisions
Before choosing a direction, we look at what you already have and what already exists. An existing tool, a better configuration or a focused integration (An integration connects your setup to software you already use, such as your email inbox.) may be the right answer.
A clear scope, risks and practical next steps
At the end you have it in writing: what to do, how big it is and where the risks lie. Then you decide what happens next.
The services in detail
These services find out what to do, before anyone builds anything.
Workflow and problem discovery
Map a workflow
We record a workflow as it runs today, with the people who do it and the documents and programs it needs. We propose nothing before we have seen it.
You get
- The workflow drawn out: who does what, with which document, in which program
- The places where it gets stuck, and which part a machine could take over
- A written next step with scope and risks
What we need from you
Some time with the people who do the work today, and a look at the real documents.
Technical feasibility and second opinions
A second opinion
There is a plan, a quote or an architecture on your desk, and you want to know whether it holds. We read it, hold it against your work and tell you what we see.
You get
- An answer to your question and the reasoning behind it, in writing
What we need from you
The documents in question, and the question you want answered.
Technical feasibility and second opinions
Security check for a website or app
For anything you did not build entirely yourself: best before launch, realistically after. The check shows what is wrong; fixing it is a separate job with its own quote.
You get
- A map of the attack surface as the site or app actually runs
- A sweep for currently known vulnerabilities in everything it is built on
- The findings, ranked by what an attacker would reach first
- A plan to fix them that you can hand to whoever built it
What we need from you
Read access, or permission to test. Your written authorisation is in place before anything is probed.
Technical feasibility and second opinions
Office network security check
What is on your network, what it exposes, what it trusts and where the credentials live.
You get
- How far someone gets from a single compromised laptop
- The findings and a plan to fix them
What we need from you
On-site access or an equivalent managed remote connection, and your written authorisation.
Architecture and build-or-buy decisions
Build or buy
Whether a ready-made tool exists, whether what you have only needs better configuration, or whether something of your own is worth it.
You get
- The options side by side: an existing tool, a better configuration, a focused integration or something of your own
- A recommendation with its reasons
What we need from you
An overview of the software you use today, and the people who work with it.
Example
An example follows once Jules has signed it off.
A small, free version of it is the interview on our home page: your report shows where your time goes and where it pays to start.
A trading desk and one deal
An example, not a client case
A commodity trader buys FOB, sells CFR and is paid under a letter of credit. The desk runs on PDFs and phone calls, and the phone calls win.
We take one deal, from the recap to the last invoice: which paper arrives where, who retypes it and what happens next. The written next step names the paper we would take on first, and what that would need.
And the Setup?
Works without a Setup
No Setup needed. You end up with a written next step.
What you end up with
A written next step: the scope, the risks and what to do next. For a security check, the findings and a plan.
Price
By scope. When the problem is still unclear, a bounded investigation is often a useful first step. A security check has a fixed scope: one system, or one site for a network. The work and the price are in a binding written quote before we start.
How to start
Four ways in, from the free interview to a written request. You choose how much you tell us first.
Where you stand
A few questions about your working day, and you see where you stand with AI and where a first step pays off. Free.
Start the interviewTalk to Jules
20 minutes with Jules in person. You tell him where things get stuck, and he tells you honestly whether and how he can help. Free.
Pick a timeAccount
Sign in with a link by email, no password needed. Pick up saved answers, download your details or delete them.
Go to your accountRequest
Rather put it in writing? Describe what you need in the form. We confirm within 2 hours and start working on it within 24 hours.
Let’s find the starting point
Or write to Jules directly in the chat on the contact page.Go to the chat
Rather roll up your sleeves? You can build the basic setup yourself, too. Do it yourself
FAQ
Questions about Figure It Out
Is this also for businesses outside trading and logistics?
Yes. If your team repeatedly copies details from emails and PDFs by hand, that work may be a good place to start with AI, whatever your sector. We know such tasks particularly well in commodity trading, logistics, forwarding, customs and compliance. The section ‘Four examples: what AI prepares and who checks it’ on the Solutions page shows four possible workflows.
Do I need to know how AI works?
No. The interview asks about your work, not about AI. Every answer is saved the moment you give it, so you can stop any time and continue later, on another device too. You can also answer the first questions in conversation with our AI assistant (An AI assistant is a chat program such as ChatGPT, Claude, Gemini or Perplexity: you write in plain language, and a language model answers.).
Do we need our own IT team?
No. We install the agreed setup and show your people how to use it. The handover document (The handover document records what we set up, how you work with it and how you back it up and restore it.) records what was installed and how the tools work together.
What if we do not buy a package after the call with Jules?
You do not have to buy a package. The interview and the call with Jules are free, and you keep your report. If we cannot help with your project, we will tell you.
Do staff need to write code or enter commands?
Staff do not need to write code. They start some workflows with a short command (A command starts a defined workflow. In Pro Setup, we set up three to five commands for your work.) we set up. Others start when an email arrives.
AI prepares a draft. Your staff check it, correct it if needed and approve it. At handover, we show them how to start workflows and check the results.
They use whatever suits them: the AI harness (An AI harness is the workspace on your computer in which AI reads files and carries out agreed steps.) on their device, the command line (The command line, also called the terminal, is a window in which you give the computer instructions by typing text instead of clicking.), a dashboard (A dashboard is an overview page, usually in the browser, that shows the state of tasks, results or figures at a glance.) or a desktop or web app. We set up what fits or use what you already have.
Figure It Out
Where does it get stuck for you?
We confirm your message within 2 hours and start working on it within 24 hours, seven days a week.