Bespoke

Standard where it's best. New development where it's needed.

We know Visma Net and finance, and we build it ourselves. If you need more than standard, we build the apps, integrations and agents on top of Visma Net, through its API. We listen first, draw the solution on a flow map and set a fixed price on it.

Book the workshop

Free workshop, 45 minutes. The flow map is yours either way. Prices exclude VAT; the Visma Net license is extra.

Starting without integrations? Visma Net Core puts all of your finances in place for SEK 75,000, and the integrations can come once the flow is right

The integrations

Systems that talk to each other. One piece of data, one place.

If the system has an open API, we connect it, whatever it's called. We draw the flow on the process map before we build, and once it's live you can see every run in our integration portal.

The breadth

If it has an API, we connect it.

We're not locked to monday.com. If the interface is open and documented, we read the documentation and build against it, whether the system was bought, inherited or built in-house. If it has no API, we ask the vendor, because more systems have one than they advertise. If that fails too, there are files and exports.

How an integration is priced

Line-of-business systems, e-commerce and point of sale

Payroll, time and HR

Warehouse, logistics and field work

Bank, payments and e-invoicing operator

Your own systems, databases and data warehouses

Visma Net's own API, which we work in every day

The flow

Data is entered once.

The same data in two places sooner or later becomes two different truths. We decide which system owns which field, and then the data moves to where it's needed instead of being keyed in again. The whole flow is drawn on the process map before we build, so you see what happens where, and where a person needs to say yes.

Book your process map

Who owns the fieldExample

Data	Entered in	Passed on to
Customer details	Line-of-business system	Visma Net
Item and price	Visma Net	E-commerce, point of sale
Invoice status	Visma Net	Line-of-business system

A field has one owner. Other systems read it; they don't overwrite it.

The visibility

You can see for yourself what went through.

Every run is logged in our integration portal. If something goes wrong, it shows what went wrong, at which step and how many records were written, and you rerun the flow yourselves once the cause is fixed. No one has to email and ask whether the file arrived.

Book the workshop

Straviont · The integration portal

Integration portal3 of 4 completed overnightExample

Flow	Run	Records	Status
Orders → Visma NetOrders from the online store	06:00	34	Completed
Time → Visma NetTime to projects	06:05	128	Completed
Visma Net → WarehouseItems and balances	06:10	0	Stopped
Visma Net → Data warehouseHistory for reports	02:00	all	Completed

Items and balances · stopped at step 3 of 4

HTTP 401 · the warehouse system rejected the call, the credentials have expired

No records were written, so nothing is left half-done. Once the credentials are renewed, the flow reruns from here.

Rerun Show full log

You get the same view we do. The alert comes straight to us, but you never have to ask what happened. Illustration with made-up flows and numbers.

How we work

We listen first. Then we build as little as possible.

No one should have to change how they work just to keep a system happy. We ask why something is done before we show where to click, and if a setting is enough, we build nothing.

We listenyour words, your flows and what chafes, not a requirements list
We adaptsettings, views, templates, approval and prices the way you want them
We connectintegrations with the systems you already run, in the direction you need
We buildapps, workflows and agents only where the standard runs out

Most often the solution lies in the first two steps, and then we say so. A project that turned out smaller than you expected is a better reference than one that grew.

Visma Net Core: the whole system for SEK 75,000

Before we build

We spec the integration together with you.

An integration that only moves data between two systems rarely holds up in reality. That's why we start with the flow, not the technology: what should trigger the run, what should happen when a field is missing or the system responds slowly, and who should know if something stops. Error handling is built in from the start instead of patched on afterward. Everything is drawn on the process map before we write a line of code, and the map is what the price is based on.

The flow first, code second · Error handling built in from the start · The map is yours, either way

The partner

We know both the finance and the technology.

Most partners do one or the other. That's why so much is still done by hand between systems.

Visma Net in depth

The subaccount, VAT zones, AutoPay, accruals, conversion. We know the corners that decide whether a setup holds for three years or starts chafing in week two.

The experience

Senior consultants who have set up finance in many companies. We recognize a flow that will chafe before it does, because we've seen it chafe before.

The industries

Installation, retail, consulting, real estate, manufacturing. Every industry has its own way of counting, and an integration that works in retail rarely does in a project-based company.

The flow, not the module

We read a balance sheet as well as a process map, and we build it ourselves. No subcontractor learning your finances along the way, and what we build, we also run.

EcE-commercePoPoint of salePaPayroll & HRWaWarehouse & WMSCRMCRMBIBI & reportsTiTime & projectsInIndustry systemFiFiles & exportTeTeams

monday.com

If it has an API, we talk to it. If there's no API, we ask the vendor for access, and otherwise there are files and exports.

Where we're heading

The line is drawn in the wrong place.

People who know finance configure systems; people who know technology build without understanding a balance sheet. That's why so much is still done by hand between systems.

With every customer we take on, the goal is the same: first a Visma Net that's set up right, then one workflow at a time until finance work stops being data entry. We're building that in projects right now, and that's why we can put a fixed price on it.

Book the workshop

Open APIis all we need to connect the system

Onceis how often data is entered, not once per system

0systems you have to replace

Your yesis required before a flow goes live

The blueprint first

You see the solution before it exists.

What Visma Net already handles, what we build, and where the systems meet. The price is calculated on the map, not on hours afterward.

Five steps, the price in the third

Step 1 · Free

The workshop

We walk through how work and money move through your business: who does what, where it takes time, what should be gone. Forty-five minutes is enough to see whether this needs to be built or just configured.

You get: 45 minutes of our time. Nothing more.

Two starting points

The same door. The same fixed price.

The workshop is free, and the map shows which path is yours. Same workshop, same map, same people: it's one track, not two offers.

Visma Net Core · price set in advance

All of Visma Net from four weeks, for SEK 75,000. Registers cleaned up and moved, bank connected, invoices going out, staff trained, all set up the way you work. Those choices are included in the price.

See what's included

Bespoke · price set on the map

Visma Net plus what's missing. For those of you with a flow no standard captures, or systems that need to talk to each other. Often added on top of Visma Net Core, in the same project.

Book the workshop

Your data, your control.

You approve, then it happens

Anything beyond reading requires a yes, and the limit on what a flow is allowed to do sits on the server, not in a setting someone could change by accident. Every write saves what's needed to roll it back.

Your keys, your environment

Integrations and apps run against Visma Net's API with your own permissions, never broader. If we build a custom system, it lives in your Azure, with your data and your keys.

Evidence for every suggestion

Every suggestion shows what the flow saw, where it saw it and why it suggests exactly that, and the log stays afterward.

Why Straviont

We share the risk. Even when we build.

Custom builds are almost always sold by the hour, and then you pay when it drags on. We set the price on the map and hold to it.

Where we stand

No make-believe prices, and the same consultant from the first call to go-live. If the standard is enough, we say so, even when it makes the project smaller.

The project model

Partial deliveries you approve, testing on your own data, training during the build. The same model whether it's four weeks or an agent in Teams.

Visma Net Core

Need the system first? All of Visma Net for SEK 75,000, or SEK 125,000 with logistics, as step one or in the same project as the build.

See what's included

7 consultants · 100% of engagements led by seniors · Same consultants from sale to go-live · we run what we build

The project model

You test with your own data
from week one.

What makes implementations long is rarely the amount of work, but the waiting in between. With us, setup, testing and training run side by side from week one, so what you find changes the configuration every week instead of at go-live.

Typical ERP project ≈ 6 MONTHS

KickoffMonth 2Month 4Go-live

The consultant configures

You're in the system

months without you in the environment

Questions about the standard flows

How we do it 4 WEEKS

Week 1Week 2Week 3Go-live

We fetch your registers, convert and import them

We configure continuously, based on your needs

You test on your own data

What you find changes the configuration every week, not at go-live

Questions about the standard flows

Processes are set together and adjusted until they fit

Automation where it makes a difference

Ongoing management, long after go-live

The environment is 75–90% complete with your own registers the first time you log in. After that, the same row appears in both models, and the difference is when it happens: the questions about the standard flows come in week two, while there's still time to act on them, instead of the morning you're due to start invoicing for real.

No big delivery at the end

You see the system take shape instead of having it presented in the final week. Whatever feels wrong has time to become right.

Training runs in parallel

Not a full day at the end that no one remembers. Every week, in the environment you'll work in, with your own data.

Standard where it's best

We start from Visma's proven flows where they give you more than your old way of working, and set up the system around your processes where those work better. If something suits you better another way, we change it within the price.

The workshop

A workshop on your flows, free of charge.

Tell us briefly about your business and we will host a free workshop where we go through how work and money actually move through your company, from order to posted and reconciled, and draw it up step by step, like the excerpt next to this. The map is yours whether or not we build it.

What you get from the workshop

The process mapYour flows drawn step by step. Yours to keep, whatever you decide.
Our assessmentWhat is worth changing on your side, and what Visma Net should be shaped around.
A planBuilt around your calendar, starting when it suits you.
A fixed priceCalculated from the map and set before you say yes.

The workshop is free. If it's not a fit, we'll tell you.

Frequently asked questions

Good to know before
we start.

How much do you customize?

As much as needed and as little as possible. We start from how you work, not from a template, but we take the steps from the bottom up: if a setting is enough, we build nothing, and if an integration is enough, we build no app. What's truly unique to you, on the other hand, shouldn't be forced into someone else's standard. Then we build, and the price is on the map.

Can we start by just forwarding an email?

Yes, and it's a good first piece. The agent gets its own address with you, and whatever comes in is handled according to the rules you've set. We usually start with one type of document, watch for a week that it lands correctly, and then open up for more.

What does a tailored solution cost?

It's on the map. The price is calculated on what needs to be built and what it needs to talk to, and it's fixed before you say yes. If you want to bring the price down, we remove steps from the map; we don't cut the quality of what gets built.

We run a system you've never heard of. Will it work?

Usually. If it has an API, we read the documentation and build. If it doesn't, we ask the vendor for access; more systems have an API than they advertise. If that fails too, there are files, exports and integration platforms. And if the integration isn't worth the money, we tell you in the workshop, not after the invoice.

Can we combine it with Visma Net Core?

Yes, that's the most common setup. Many run Visma Net Core first precisely to see what actually needs to be built. Once the system is set up right, the map is both easier to draw and cheaper to build.

How is this different from the adjustments included in Visma Net Core?

Settings and flows inside Visma Net we change within the price, because changing course costs us nothing. Bespoke is what doesn't exist in Visma Net: an app, an integration, an automation, an agent. It gets built, and that's why it has a price, set on the map.

Who owns the solution, and what happens when Visma updates?

You own it. If we build a custom system, it lives in your environment, with your data and your keys, and the code is yours. We run what we've built and keep up with Visma's API changes. That's our job.

Standard where it's best. New development where it's needed.