Getting started

About Solvimon

Answers to common questions about Solvimon: what it is, who runs it, and where it fits compared to building billing in-house or patching together point solutions.

What is Solvimon?

Solvimon is an API-first pricing and billing platform built for pricing complexity that most billing tools can’t handle: multi-dimensional usage pricing, hybrid subscription and consumption models, mid-cycle plan changes, and enterprise-specific contract terms.

Solvimon covers the full quote-to-cash flow:

  • Usage metering, from raw events to billable meters
  • Pricing plan configuration (usage-based, recurring, per-seat, one-off, top-up)
  • Customer and subscription management, including multi-entity roll-ups
  • Invoicing, credit notes, and refunds
  • Payment collection and dunning across processors like Adyen
  • Revenue and usage analytics

Every operation available in Desk is also available through the REST API, so you can run billing headless or manage it operationally without engineering involvement.

What kind of billing complexity does Solvimon handle?

Solvimon is built for the cases that force teams into custom engineering or a patchwork of point tools:

  • Hybrid and multi-dimensional pricing – usage-based, seat-based, and flat pricing on the same plan, with tiered and volume-based rates.
  • Mid-cycle amendments – upgrades, downgrades, and plan changes that need to be prorated correctly mid-billing-period.
  • Credit notes and refunds – corrections to finalized invoices without breaking your accounting trail.
  • Payment status sync – dunning on Adyen, and reconciling slower payment rails like bank transfers.
  • Multi-entity billing – roll-ups across subsidiaries, currencies, or business units.
  • Enterprise contract terms – custom pricing negotiated per deal, without turning every contract into a one-off engineering project.

If your pricing model, invoicing rules, or contract terms are the reason billing keeps landing on your engineering team’s roadmap, that’s the problem Solvimon is built to take off it.

Does it work with my stack?

Yes. Solvimon is designed to sit alongside your existing finance and data stack rather than replace it:

  • API-first – every Desk action has a corresponding REST API endpoint across the Configuration, Identity, Transaction, and Event domains.
  • Downstream integrations – pull finalized invoices directly, or sync transaction journal entries into your accounting system.
  • Flexible data model mapping – Solvimon adapts to how your product already represents usage, invoice states, and state transitions, instead of forcing a rewrite on your side.
  • Fast to stand up – a typical implementation is sandbox setup, pricing alignment, and roughly two weeks to go live; simple greenfield setups have gone live in as little as two days. More complex enterprise rollouts are supported on a longer timeline.
See Onboarding & tutorials for a step-by-step implementation path.

Who’s behind Solvimon?

Solvimon was founded by two people who spent years building billing infrastructure at Adyen before starting the company:

  • Kim Verkooij – Co-founder & CEO. Previously VP of Product at Adyen, where he oversaw the billing platform and managed the quote-to-cash process across monetization, international taxation, and revenue assurance.
  • Etienne Gerts – Co-founder & CTO. Founding team member at Adyen with 13 years of tenure, where he grew the engineering organization to 25-30 teams while staying involved in the billing engine.

That background is why Solvimon is built around the assumption that pricing complexity is the norm, not an edge case to special-case around later.

Who uses Solvimon?

Solvimon is used by fintech, payments, and SaaS companies including Yapily, Montonio, SEON, Gigs, HAWK:AI, and Tebi, along with a growing set of AI companies pricing usage- and outcome-based products.

AI startups get the first $3M of billing volume free. Contact Solvimon for current terms.

How does Solvimon compare to building billing in-house or stitching together point tools?

Most teams don’t choose complex billing logic on purpose; they end up there because a customer negotiates a custom deal, or a pricing model needs a usage dimension no off-the-shelf tool supports. At that point, the options are usually: build and maintain it in-house, or accept “whatever’s easiest to implement” as your pricing strategy instead of what’s actually best for the business.

Solvimon exists so that trade-off doesn’t have to happen. It’s positioned to be the layer that absorbs mid-cycle amendments, credit notes, multi-entity roll-ups, and negotiated enterprise terms, so pricing and packaging decisions stay driven by go-to-market strategy, not by what’s cheapest to build.

Where do I start?