SYNATRAIL FOR COMPANIES

The pre-study.
In days, not months.

Every project starts with an idea nobody understands yet.
Today, working it out takes months of meetings.
Here it takes one shared board and ends in one document.

RUNS ON YOUR SERVERS · YOUR MODELS · YOUR DATA

SCROLL TO EXPLOREIDEA × BOARD × DECISIONUTC --:--:--
SOUND FAMILIAR?THE PRE-STUDY TODAY

One idea.
Five departments.
No answer.

Someone has an idea. Nobody knows what it really is. That is not the problem. Working it out is.

  1. 01

    A stakeholder heard a term and wants a result.

    They mix up what they heard. Nobody knows what they actually need.

  2. 02

    The investigation lives in email, slides and people’s heads.

    Every department has a piece. Nobody has the whole picture.

  3. 03

    Months pass. Thousands of euros. Still no clear yes or no.

    Architects, stakeholders and consultants, all waiting on each other.

  4. 04

    When the answer comes, nobody can show how it was reached.

    The reasons are gone. The next project starts from zero again.

ONE PRE-STUDY, SIX MONTHSILLUSTRATIVE EXAMPLE
Six months of hand-offs, then the same idea decided in two weeksAlong a six-month axis, a stakeholder request in month one waits for an architects’ workshop in month three, which waits for IT and legal in month five, and month six ends in an open question. Below, a straight line runs from the same idea to a decision made on one board in week two, with every reason kept. TODAY · MONTH 1MONTH 6 WAITSWAITS 01 / STAKEHOLDER · MONTH 1“We need AI.” 02 / ARCHITECTS · MONTH 3Workshop.Still no scope. 03 / IT & LEGAL · MONTH 5No API.Where’s the data? ?STILL NO YES OR NOThousands of euros later. THE SAME IDEA, ON ONE BOARD Every team on the board from day one. WEEK 2 · ONE DOCUMENTDecided in week two.Every reason kept.
Six months of waiting on each other, or one board and one decision.
HOW IT WORKSFOLLOW THE THREAD ↓

One board.
Everyone on it.

Bring the idea. Bring the people who know something.
Leave with one document.

  1. 01 / THE IDEA“We should do…”Half-formed is fine.
  2. 02 / THE BOARDWork it out together.Sources, questions and answers in one place.
  3. 03 / THE DECISIONEvery choice keeps its evidence.Anyone can see why.
  4. 04 / THE DOCUMENTOne document out.Approve it, or hand it to the builders.
SESSION / THE PORTAL PRE-STUDYILLUSTRATIVE TRANSCRIPT
> new investigation "we need a customer portal. with AI."  + request    Stakeholder · month 1                                  01  + data       Support tickets, last year · invoice · status          02  ! challenge  IT: the ERP has no API                                open  ! challenge  Legal: where does the data live?                      open> ask agent "do they want a portal, or just answers?"  = answer     2 sources · 1 contradiction · not a portal> decision document  ✓ portal/     decision.md · problem · system · go / no-go · evidence (6)
01 / THE SHARED BOARDIDEA → EVIDENCE

Every team.
One board.

The stakeholder’s request. The support tickets. What IT knows about the old system. What legal needs. All on one board, connected.

Ask the AI about a selection, send it to research, or test a claim against your own data. Challenges stay visible until they are answered. The team decides what holds up.

OUR EXAMPLE STARTS HERE
“We need a customer portal. With AI.”
THE PORTAL PRE-STUDYILLUSTRATIVE EXAMPLE
A request becomes a connected investigationA stakeholder request for a customer portal and a chart of support tickets connect to a sharper question: do customers want a portal, or just answers? IT’s objection that the ERP has no API and legal’s question about where the data lives stay visible as open points. 01 / STAKEHOLDER REQUEST“We need a portal.With AI.” 02 / SUPPORT TICKETS, LAST YEARWhat customers ask.INVOICESTATUSLOGINOTHER 03 / THE REAL QUESTIONDo they want a portal,or just answers? INFORMSCONTRADICTS ?IT: “THE ERP HAS NO API.”Raised in week one. Still visible. ?LEGAL: WHERE IS THE DATA?Open until answered.
Connect what each department knows. Challenge the request. Keep the reasoning.
02 / THE DECISION DOCUMENTEVIDENCE → DECISION
STAKEHOLDERSARCHITECTSEVIDENCE
DECISION DOCUMENT / 001
THE PORTAL PRE-STUDY

Not a portal.
An answer engine.

Answer invoice and status questions where customers already ask them.

01Who asked & what they needTHE PROBLEM
02What we would build & howTHE SYSTEM
03Go, no-go, or not yetTHE DECISION
EVERY LINE CITES A CARD↳ READY FOR THE STEERING COMMITTEE
Illustrative document · Your board supplies the content.

The whole pre-study.
One document.

Select what held up on the board. Create the document. Nothing in it is there without a reason you can click on.

  1. 01

    A reason to do it, or not.

    The problem, who asked, what they actually need, and the evidence behind it.

  2. 02

    A plan that fits your systems.

    Architecture, modules, dependencies and a sequence for the build. Written against what IT already knows.

  3. 03

    A way to know it works.

    Testable requirements, the risks, and the questions still open. Six months later, anyone can see why the decision was made.

03 / YOUR DATAHOSTED IN YOUR ENVIRONMENT

Your servers.
Your models.

Your licensed installation runs on your infrastructure. You bring and pay for the models you choose. Your board, files and decisions stay in your own database; the installation exchanges usage data with our systems daily for licence reconciliation.

  1. 01

    Your own installation

    Runs with Node.js or Docker on a server you control. One database, one private file store, your own accounts.

  2. 02

    Your own model keys

    Connect OpenAI, Anthropic or Gemini with your company key, or use Claude Code. Set the research budget. Decide what the AI may read.

  3. 03

    Nothing public unless you say so

    Boards are private by default. Publishing anything is a deliberate step, and it can be withdrawn.

OpenAIAnthropicGeminiClaude CodeSUBSCRIPTION
Your installation.YOUR SERVER · YOUR DATABASE · YOUR FILES
Your workspace stays in your installation. Model requests use your provider keys; licence usage is reconciled daily.
04 / THE COMPANY LICENCEONE COMPLETED INVESTIGATION = ONE UNIT

One annual licence.
Room to investigate.

Usage is counted when an investigation is complete. Each day, your installed container exchanges usage data with our systems. We reconcile completed investigations against your allowance and any additional packs, then calculate any overage.

  1. 01

    A substantial allowance, included.

    Your annual self-hosted licence includes a substantial number of investigations.

  2. 02

    One completed investigation, one unit.

    Model calls, tool steps, clicks, retries and resumed sessions do not count as extra investigations.

  3. 03

    More when you need it.

    Purchase additional investigation packs as your included allowance runs low.

  4. 04

    Your models and infrastructure.

    You continue to pay your own model providers and run the installation on your own infrastructure.

TALK TO US

Which idea is stuck
in a pre-study right now?

Tell us about it. We will show you how it looks on the board, and what it takes to run Synatrail inside your company.

Synatrail is built and run by Blacksquid Engineering. Read how it started.

Who is this for?

Teams that decide what to build: product, architecture, innovation and the stakeholders who bring the ideas. If your company runs pre-studies, feasibility checks or discovery phases, this is for you.

Does it replace our architects?

No. It gives them one place to work, and a document that shows their reasoning. The people stay. The months of chasing information go.

Where does our data go?

Your board, files and decisions are stored in your own installation. Your chosen model providers receive the material sent in model requests. Our systems exchange usage data with your installation daily to reconcile completed investigations.

What does it cost?

An annual self-hosted licence includes a substantial investigation allowance. Each completed investigation uses one unit, regardless of model calls, tool steps, clicks, retries or resumed sessions. Buy additional packs as needed; our systems reconcile usage daily and calculate any overage. You pay separately for your own models and infrastructure. Contact us for a licence quote.