Build once. Publish where you already publish.

A tool for building guides that lead a visitor to an answer.

You build a decision tree — question, answers, rule, result — by dragging nodes onto a canvas. A visitor gets one question at a time and an answer at the end. The guide is published on your own site.

Built for government agencies, municipalities, housing companies and businesses: self-service, support guides, onboarding and decision support.

No code, and the person who knows the rules is the one who publishes them. If something goes wrong you open last week's version and publish that. Why Flowweaver exists

Try the guide Rebuild the guide

How it works

The buttons at the top are the steps: try the guide as a visitor, then open the same guide in the editor. Want the editor explained first? Read Getting started with the editor.

What a result becomes

A guide ends in a result. It is rarely just a piece of text — usually it is the start of something.

An answer carrying the visitor's own values The amount that was calculated, the date that applies to them, the name they typed — the result says you can apply, and roughly how much rather than something general.
A finished email Recipient, subject and body are filled in by the guide from what the visitor answered. Either they send it, or your system sends it for them.
A head start on the next step Your page can take everything the visitor answered and the path they took. The form afterwards does not have to ask the same things again.
A call to your own systems A calculation or a lookup can run on the server mid-flow, and the answer travels on through the guide.

Why Flowweaver

Most tools for this are built by developers, for developers. The editor learns their words and fills in fields shaped after the database rather than after the work.

What follows is caution. You do not touch what you do not understand, and the day a rule changes there is no time left to become brave in.

Flowweaver is built the other way round, and nearly all of it comes down to one thing: it should be easy to change your mind.

A guide nobody dares to edit is a guide that goes out of date.

What that means in practice, for you as an editor:

Go back to the version that worked Something breaks after an edit. You open the version that worked and publish it — visitors are back on it, and you never had to remember what you changed. Trying a variant is just as cheap: write in a copy while people keep reading the published one.
Update it yourself when the rules change When a regulation changes you correct the guide right away and republish — no developer in the loop, no waiting for the next release.
The right calculation, the same every time Fees, allowances and thresholds are calculated in the guide itself with formulas — no code. The visitor gets the right answer, consistently.
Review the whole flow before you publish Walk the guide step by step, see every path a visitor can take and which values each one works out. Catch the mistakes before a visitor does.
Sensitive assessments never leave the building Build rules and calculations visually and run them on the server — the logic never reaches the visitor's browser. Built to OWASP principles, with data minimisation in line with GDPR.
Connect a calculation you already have Ask your web developer for the calculation itself, on the server. You wire it in with a link, pick which values go with it, take the answer back into variables and carry on through the flow. Save the control as a template and it is there for the next guide.
Accessible from the start Built for keyboards and screen readers, with the Swedish accessibility act and EN 301 549 as the basis.
One guide, your channels The same guide runs in SiteVision, as an e-service or standalone. Connect your own APIs, and export/import as JSON for version control.

A guide is content, not a system

Other tools put your guide somewhere else: behind their login, in their database, exported if you ask nicely. Flowweaver makes it a piece of content in the site you already publish in — versioned like content, translated like content, owned like content.

Every guide is a JSON file Yours to read, keep, hand to a colleague, or take somewhere else. Nothing is stored by us, because there is no us to store it.
It lives where your pages live A file in the archive, a row in your database, a document in your CMS. You choose, and the same guide runs either way.
No new platform to move to No account, no migration, no second place for editors to learn. The guide sits inside the site they already work in.
Leaving costs nothing Stop using it and the guides are still yours, still readable, still JSON. A promise worth making only if the product is good.
Versioned like content Every save is a version you can go back to, with a note on why you kept it. Publishing moves the green mark to another version, and anything you write in an unmarked row never reaches a visitor. See what working in it is like.

Two ordinary custom elements, standard in every browser — so a guide runs in an ordinary page, whatever framework it is built with. We have run it in SiteVision and standalone; the rest is the browser's job rather than ours.

Five reasons, five proofs

Five of the reasons above, and the proof for each one — in the tool, in a minute and a half.

The film in text

Content, not development: the question in a finished guide is rewritten right in the editor — no ticket, no code.
The preview does not lie: the guide is run at once, and the rewritten question is there word for word.
You can change your mind: on the versions page an earlier version is published again — the visitor's pane switches the same moment.
Accessibility is built in: a guide is answered with the keyboard alone — focus visible, one question at a time.
The data is not stuck: File → Export guide, and the whole guide leaves the tool as a file in a standard format — a safe copy, or something to read into another guide.

Thirteen more films: how it works in four steps, a guide built from an empty canvas, the routes through a finished guide, versions that make changing safe, one more language, a guide that counts while you answer, the editor without a mouse, twenty-four nodes — and the viewer running on your page from a single tag. Watch the films.

More examples and features

Five organisations, five guides — find your everyday among the use cases. Below: every editor variant, viewer and module.

Getting started

Decision guides with questions, options, rules and results — the foundation of Flowweaver, and enough for most guides.

Find the right e-service A wayfinder: a few questions that lead to the right e-service or guide — before the visitor opens the wrong form. Rebuild Try
Might you be eligible for housing allowance? A couple of questions, one rule and an answer straight away — the story from the start page. Rebuild Try
A simple guide The stripped-down editor, and the guide it produces. Start here if you are building your first. Rebuild Try

More things to use it for

The same idea — questions, rules and results — works in quite different settings, such as advice for new businesses.

The printer will not print A troubleshooting guide: four branches, twenty-four nodes, and the answer is something to do rather than an amount. Rebuild Try
Which company form suits you? A decision guide for new businesses: a few questions branch to different suggestions. Rebuild Try

Companies

The examples here are built for companies rather than a municipality — the same questions, rules and results, in a private e-service. Each one is also a template: open it, rename it, save it as your own.

Insurance claim A claim at a made-up insurer: the policy from the register, follow-up questions per type of damage, the place on a map, pictures — and the compensation after the deductible worked out as you type. Rebuild Try
Quote request A painting firm asks what it has to know before quoting — the trade, the rooms and the area — and works out a rough estimate as the customer types. Rebuild Try
Booking request A salon without a calendar: the service out of the firm's own list, two days that would work, and an email draft to answer — nothing is booked until somebody answers. Rebuild Try
Membership application An association where the kind of membership decides both who is covered and what it costs: the family is added a line at a time, and the fee stands beside the consent. Rebuild Try
Complaint An online shop where the order and the item come from the register and every fault has its own follow-up — two rules in a row, so both the torn seam and the wrong size get asked about. Rebuild Try
Conference registration Several participants, a page each, and a booking that becomes a place in the queue when fewer places are left than you asked for — the number of places lives with the organiser, not in the guide. Rebuild Try
Notice to move out A housing company where the notice period comes from the contract rather than the form — and the days of rent are counted while the tenant picks the day. Rebuild Try

Surveys

Questions answered on a scale, several on one page — the same tool and the same submission as the guides.

How do you like living here? A housing company's tenant survey: a way to decline right at the start, three ratings on one row under a heading, a 1–10 rating on its own page, a follow-up question when the rating is low, and an average in the thanks. Rebuild Try

Business logic

When the guide has to calculate something or collect details: variables, formula calculations and field validation.

Borrow A slider for the amount, − / + for the term — and the monthly cost recalculated while the visitor answers. Rebuild Try
Housing allowance – calculation A calculation node works out a preliminary monthly amount, and a rule branches on the result. Rebuild Try
Housing allowance – details Identity number, housing cost, floor area and income — with format validation and limits that catch mistakes at once. Rebuild Try
Variables, rules and validation The editor with everything switched on, and the same guide run one question at a time. Rebuild Try

Advanced flows

E-services with several fields per page, the Page Builder, email results and secure execution on the server.

An e-service with pages and fields Several fields are answered on one page instead of one question at a time. Rebuild Try
Page Builder Responsive pages with fields, texts and blank rows — and the same page rendered as a service of its own. Rebuild Try
Secure execution (a simulated BFF) The same e-service run through a backend-for-frontend. The client gets formula-free view models — the calculation and the rules stay on the server. Rebuild Try
A place on a map “The streetlight by the playground” can be pointed at although it has no address: a point, several points or a drawn area — through the host's own map service, not a bundled one. Rebuild Try
The whole editor The editor with no profile limits, and the same guide run with earlier answers visible above the current step. Rebuild Try

Show every example

Fault report A fault report end to end: contact details on one page, the place on a map, a category from a lookup, a photo with marks, and the problem in the resident's own words. Rebuild Try
Several countries from a closed list A field picking several countries from the Swedish Tax Agency's codes, and a rule branching on the codes rather than the names. Dual citizenship is ordinary — try Denmark and Turkey together. Rebuild Try
One municipality, and the code behind the name The same kind of list, a single answer: one municipality from Statistics Sweden's 290, and a rule testing the code rather than the name. The result prints both parts, so what an answer with parts is can be seen. Rebuild Try
Add a code list of your own For whoever integrates: four lines that fetch a JSON file and register it, with the source beside the guide that uses it. Nothing is bundled — a list is something you add. Try
Walkthrough: build a question guide A step-by-step with screenshots showing how to set up a simple guide. Try
Email result with an attachment Produce an email draft and get the attached file back with it — nothing is uploaded and nothing is sent. Try
Submission and receipt Review the answers, submit and get the receiver's reference number — and see the honest failure when the receiver rejects. Nothing is sent. Rebuild Try
Order forms A repeating page instead of a folder tree: the visitor picks a form from a lookup, says how many and adds more. A review per page and an email that counts them. Rebuild Try
The recipients The publisher's half: the catalog with addresses, the default recipient, and why the address never reaches the browser. Try

Embed Flowweaver on your own page

Two ordinary custom elements — the viewer that runs a finished guide, and the editor an author builds it in. No framework required.

Read the installation guide

Four pages that run real code instead of showing snippets: the smallest correct setup, languages in the host system, a calculation on the server and versions of a guide, wherever you keep them.

The quickest possible start

<script src="https://flowweaver.se/lib/flowweaver-viewer.global.js"></script>

<guide-preview></guide-preview>

An ordinary script tag — no build step
Rolling latest; point at a version in production
The viewer weighs 53 kB gzipped
Also available as an npm package with TypeScript types