Forneus Technologies / Regulated Automation
VASSAGOEuropean Legal-Tech Control Layer
Poland / Italy / Switzerland / Spain / Canton-aware routing / Credit-based access / Guarded premium tracks
Vassago compresses bureaucracy into structured execution. The product owns identity, billing, storage, policy, market context, and legal framing before any workflow is allowed to act. Users buy one balance, enter one shell, and reach 78 mapped routes without opening a new microsite for every country, permit, tax form, or regulated edge case.
Identity, balance, and policy before AI execution
Every request is validated for project access, country, optional canton, private upload policy, and credit reservation before the downstream worker sees a single byte of intent.
Not a law firm. Not a static calculator. Not another country guide.
Vassago sits between expensive human advisory and shallow content portals. It turns high-friction public rules into repeatable, auditable, multilingual, credit-priced workflows with partner handoff for the routes that should never remain fully autonomous.
The product exists because fragmented public rules are still sold as human time
Local consultants monetize latency, static comparison portals monetize attention, and users pay for confusion. Vassago monetizes structure: one intake layer, one routing policy, one wallet, and many country-specific legal outputs behind it.
One person, five bureaucracies
A foreign worker in Switzerland may touch permits, payroll tax, social insurance, rent law, and health insurance in the same quarter. Today that means five search journeys, three consultants, and zero shared context.
Vassago keeps that context inside one account and one policy envelope.Swiss canton logic raises willingness to pay
The Swiss lane is not just another geography. Canton, language, and regulated workflow differences create a premium route where pricing, partner escalation, and defensible legal positioning all become stronger.
That is why CH is the highest-yield wedge in the current portfolio.One core can sell many routes
The project does not add value by building 78 isolated products. It adds value by converting one secure execution stack into many country-aware workflows with deterministic inputs, citations, upload policy, and auditable result delivery.
That is how Vassago scales without turning workflow expansion into operational chaos.Why Vassago can become a strong company, not just a useful legal-tech tool
What matters to a fund is not that bureaucracy is annoying. It is that Vassago sits on repeat demand, premium trust routes, localized pricing, and one control shell that can sell many workflows without fragmenting into country-by-country microsites.
SMB compliance and relocation do not happen once
Tax, payroll, permit, insurance, tenancy, and invoicing routes pull users back repeatedly. That gives Vassago a much stronger repeat-usage profile than one-off content or static comparison portals.
The user life cycle is long enough to support wallet reuse and route expansion.Low-friction traffic can coexist with premium guarded lanes
Poland and Spain can drive acquisition, Italy can monetize administrative density, and Switzerland can hold the premium legal-tech ceiling. That gives one shell multiple pricing personalities instead of one blended low-margin product.
The best products here do not flatten price; they stratify it.The moat is route governance, not generic AI output
Identity, wallet logic, route metadata, canton-aware dispatch, upload policy, partner escalation, and guarded premium workflows form the durable layer. A chatbot can be copied faster than a regulated execution shell with local logic.
Control-plane depth is the real moat, not prompt decoration.One secure core can monetize dozens of routes
Vassago does not need 78 separate products to monetize 78 routes. One account system, one request model, one wallet, and one policy layer can compound across markets, which is exactly the kind of leverage investors want to see.
The shell scales breadth faster than service businesses scale headcount.Four markets. Four different monetization personalities.
Vassago is valuable because it does not flatten Europe into one compliance template. Each market has a different trigger, price ceiling, and trust pattern. The shell normalizes execution while preserving local commercial logic.
Poland
Tax panic, invoice mandates, grants, AML, labor, and expat paperwork create repeat demand for low-to-mid ticket routes that can later upsell into premium contract and interpretation work.
Italy
Italy rewards workflow compression. PEC, SdI, debt recovery, privacy, and labor obligations are not glamorous, but they are expensive in human hours and ideal for structured execution.
Switzerland
The premium lane. Canton-aware tax, permits, tenancy, FINMA, company formation, and cross-border payroll questions create the strongest willingness to pay and the clearest need for guarded partner escalation.
Spain
Migration, digital access, tax regimes, rental protection, and autonomo bureaucracy form a large consumer entry lane with strong conversion into tax, landlord, and partner-led legal products.
Market density is visible in route mix, pricing power, and trust load
Vassago is strongest where the route count, repeat demand, and governance burden overlap. That is why Switzerland leads pricing power, Italy leads administrative friction, Poland drives SMB volume, and Spain accelerates migration-led acquisition.
Current coverage by mapped module count
The route map is already balanced enough to support one shell while keeping each market commercially distinct.
Commercial intensity by trust and ticket ceiling
This is a positioning scorecard, not public market share. It highlights where Vassago can monetize structured trust faster.
Largest revenue density in the TAM model despite the smallest SME base because canton-aware routing and premium workflows raise price ceilings.
Tax, invoicing, payroll, and compliance workflows form the biggest modeled demand family and give Vassago recurring usage instead of one-off legal traffic.
Foreign-born and foreign-resident users across the launch geographies create a second acquisition engine that feeds higher-ticket admin and legal routes.
One balance and fixed credit packs simplify monetization across countries while keeping room for guarded premium pricing where the route carries real risk.
The moat is not just AI. It is routing, pricing, and safety posture.
Most alternatives win in only one dimension. Vassago is built to win the full chain: discover, qualify, route, compute, store, cite, deliver, and escalate.
| Category | Typical offer | Speed | Country depth | Document handling | Commercial weakness | Vassago advantage |
|---|---|---|---|---|---|---|
| Big Four / top advisors | High-cost bespoke advisory | Days | Deep but expensive | Manual and partner-driven | Too slow and too costly for routine panic | Vassago takes the lower and middle layer of demand before partner counsel is required |
| Local comparison portals | Static calculators and lead generation | Instant | Shallow | Usually none | No workflow continuity and no nuanced edge cases | Structured intake, uploads, policy logic, and downstream result delivery |
| Single-country legal bots | One topic, one geography | Minutes | Narrow | Ad hoc | Microsite sprawl and duplicated acquisition cost | One shell, one wallet, one dashboard, many routes |
| Expat forums and consultants | Mixed anecdotes, manual support | Unreliable | Experience-based | Email chaos | No auditability and no reusable structured context | Canton-aware, multilingual, repeatable output with guarded escalation |
| VASSAGO | Credit-priced legal-tech operating layer | Async 202 + structured return | PL / IT / CH / ES | Private uploads + short-lived signed access | Needs careful launch governance on premium routes | Blue-ocean hybrid of product shell, workflow engine, and partner-safe legal escalation model |
Commercial rollout should follow trust, not just feature count
The right sequence is not "publish every route." It is: harden the shell, monetize the repeat lanes, guard the regulated tracks, and only then widen geography.
Identity, pricing, request studio, and canonical route registry
The site already frames the right control model: one account, one wallet, one request lifecycle, private uploads, structured project metadata, and country-aware dispatch rules before execution.
Launch the repeat-demand lanes that create habit
Start with routes users come back to: tax filing support, permit logic, payroll-facing questions, KSeF panic, tenancy, and seasonal insurance / filing windows. This creates data, trust, and wallet behavior before guarded legal lanes expand.
Bring in FINMA, company formation, IP Box, and partner counsel routing
These routes are where pricing strengthens, but so does risk. They should remain guarded, approval-aware, and connected to human partner handoff with explicit informational-service positioning.
Scale into approvals, org workspaces, incident policy, and provider posture routing
The long-term moat is not the chatbot. It is the audited control plane that lets B2B customers route requests, approvals, premium evidence, and delivery policy through one managed legal-tech system.
The strongest routes are painkillers first, knowledge products second
High-conversion legal-tech products do not start with abstract law. They start where time, money, and rejection risk collide.
KSeF, JPK, and filing stress before deadlines
SMBs and accounting teams do not need theory when filing pressure hits. They need validated structure, draft outputs, and a path that removes fear of format mistakes.
Structured filing utilities that feed premium reviews
Low-friction compliance tools generate repeat visits, create wallet behavior, and surface the users who later buy premium contract, grant, or interpretation work.
Permits, payroll tax, canton rules, and company formation
Switzerland is high-trust and high-friction. Small differences between cantons, permits, and regulated sectors justify stronger pricing and stricter verification flows.
Canton-aware logic with guarded escalation
Market, local jurisdiction, route type, and premium posture determine language, delivery contract, and whether partner counsel must enter the loop before final delivery.
NIE, TIE, digital nomad tax, rental protection, digital access
Spain concentrates fear, paperwork, and life friction into a small set of resident workflows that users search for urgently and share socially.
Consumer entry lane that expands into tax and B2B services
The migration lane drives acquisition, then converts into autonomo, invoicing, landlord, and cross-border tax routes as the user settles into the market.
FINMA, token classification, Patent Box, and partner-led legal review
Some routes create large economic value and large liability if positioned recklessly. They cannot be sold like static calculators.
Guarded workflow, audit trail, explicit disclosure, human oversight
Premium routes stay behind stronger verification, approval-aware delivery, and clear informational-service disclaimers with optional partner-lawyer handoff.
TAM, SAM, and SOM are large because the shell spans both SMB compliance and migrant friction
The market model below is intentionally conservative. It values the launch footprint as a workflow market, not as the full legal-services market. The opportunity comes from digital execution layers replacing fragmented search, email, and junior advisory time.
Total annual addressable workflow market across the four launch geographies, combining SME compliance demand and high-friction migration / resident administration workflows.
Serviceable digital segment reachable with the current route architecture, wallet model, and partner-safe positioning in the first commercial pass.
Modeled medium-term obtainable annualized run-rate if Vassago captures a low single-digit share of the reachable digital segment through repeat routes and premium guarded lanes.
Where modeled revenue density is strongest
Swiss premium routes distort monetization upward even though Switzerland is the smallest launch market by company count.
Which workflow families carry the modeled TAM
Modeled on the current launch footprint of 9.5M+ SMEs and 17M+ foreign, migrant, or expat residents in the covered geographies.
Launch-footprint facts used in the model
The consumer and relocation lane is already large enough
Vassago decision architecture
The point of the architecture is not to make AI louder. It is to make execution safer, cheaper, auditable, and commercially coherent across four markets with very different legal stakes.
Identity and wallet gate
Auth, session, organization context, role, and available balance are resolved before any route can reserve credits or touch a worker lane.
Market and route framing
Market, optional local jurisdiction, route type, language, and premium posture define which rule set, references, and disclosures must govern the request.
Structured payload builder
The shell normalizes inputs, masks sensitive data when needed, resolves protected document access, and emits a structured execution contract instead of raw conversational noise.
Country worker execution
A narrow, stateless execution contract reaches the correct market lane. Country workers stay isolated so one release or queue spike does not poison the full system.
Result locker and audit trail
The response returns into the product shell, not straight to the browser. Credits settle, result tabs populate, delivery rules apply, and guarded routes can pause for human review.
Commercial design needs visible pricing logic, not only text claims
Vassago should show how pack pricing shifts by purchasing power and trust intensity across the four launch markets. Switzerland keeps the premium ceiling, while Poland, Italy, and Spain need localized entry ramps that still preserve room for guarded high-value routes.
Entry-to-business pricing by market
The graph below normalizes each country ladder to show relative steepness. Switzerland stays the highest-ticket path, while Poland is compressed for SMB adoption and Italy / Spain sit in the mid-market euro band.
Where value lands inside the route portfolio
Different markets bring different mixes of low-friction traffic, repeat admin demand, and premium legal escalation. The chart shows why the product can stay broad without flattening margins.
What the stack actually does
Vassago is not a brochure for future automation. The stack already defines how identity, pricing, route metadata, uploads, worker dispatch, and premium safety posture should coexist.
One wallet. Country-localized ladders. Premium logic where the stakes justify it.
The credit model is a strength, not a shortcut. It lets Vassago sell low-friction entry routes without creating plan chaos, while still protecting high-margin legal and regulated tracks behind guardrails.
Credits unify B2C urgency with B2B depth
A permit, invoice, tenancy, or tax question should not force the user into a new billing relationship each time. Vassago centralizes value capture, then allocates it per route through known credit costs, localized market ladders, guarded pricing, and partner escalation where needed.
Same wallet model, different entry pressure by country
Examples from the current route map: Contract Intelligence (100 credits), FINMA Compliance (90), Swiss company formation (60), CH Patent Box (95), PL IP Box (premium lane), and canton-aware permit or cross-border payroll workflows. The pack ladder should stay structurally consistent while market currency and entry friction adjust per geography.
Swiss reference entry pack for first requests, diagnostics, and low-risk single-route use.
Swiss reference mid-tier optimized for repeat use across several routes and one active market.
Swiss reference pro tier for users who handle documents and regulated workflows weekly.
Swiss reference business tier for HR, FinTech, relocation, and partner-led B2B operating teams.
Information service first. Human oversight where it must exist.
Vassago should remain positioned as an information and analysis layer. The product becomes commercially stronger, not weaker, when it explicitly distinguishes between autonomous support, guarded review, and partner-counsel escalation.
The route mix is unusually strong because it combines repeat consumer friction, SMB compliance necessity, and a Swiss premium wedge with partner-safe monetization.
What Vassago removes from the market
The product should feel like a replacement for waiting, guessing, and retelling your case from zero on every new route.
Advice latency turns routine panic into premium invoices
Users wait days for answers on filing, permit, or rent issues that should be routable in minutes.
Structured, country-aware request execution
The shell captures the case once, then routes it to the correct project and legal frame immediately.
Region-specific rules are hidden behind generic national content
Static portals flatten canton, province, and local-office differences until the user hits a rejection or penalty.
Country + canton + route drives the output contract
Switzerland in particular needs routing logic that changes language, references, premium posture, and partner review behavior automatically.
Uploads and sensitive data are handled casually by most legal-tech products
Files are often mixed into chat threads without clear retention, masking, or result-delivery policy.
Private storage, short-lived access, masked logs, result lockers
Workers should only receive the minimum contract needed for execution, while the shell keeps the durable system state and delivery controls.
High-value legal and regulatory routes are sold without adequate safety rails
That creates liability, weakens positioning, and prevents serious B2B adoption in the highest-margin workflows.
Guarded routes, explicit disclosure, and human-in-the-loop review
Premium workflows should feel stricter by design. That is part of the product quality, not friction to be removed.
Vassago is the missing layer between legal expertise and executable product
It turns public rules, local edge cases, and recurring admin pain into structured, auditable, multi-market workflows that users can buy with one balance and operate from one account. That is why it deserves to sit beside the rest of the Forneus ecosystem as a first-class project.