Founding qaryon: an idea carried for years, a first client who opened the door

I had the idea for qaryon long before qaryon.

For years, I wanted my own structure: to design an architecture and deliver it myself, without handing it to someone else halfway through. What was missing was not the drive. It was a first client willing to trust a real mission to a one-person structure. That client came in Switzerland.

This piece tells how qaryon was actually founded: a mature idea, a real opening, and the leap.

Leaving for Switzerland

Twelve years with telecom integrators and carriers, designing architectures others had to deploy, then putting drifting projects back on track. My ground never moved: enterprise and carrier voice. UCaaS and CCaaS, SBC and IPBX, carrier interconnection, provisioning automation. Those are the years that produced a UCaaS platform for a multi-site group of 16,000+ users, and provisioning cut from several hours to a few minutes per site.

Those twelve years taught me one thing above all. The architect who designs is almost never the one who deploys. A senior scopes the pre-sales, a junior inherits the go-live, and the client discovers the gap in production, on the invoice or on the quality of service. I saw that cycle enough times to want out of it: to hold both ends, from design to production, under a single responsibility. That is where the idea for qaryon came from, long before the structure existed.

Switzerland was a long-running telecom mission at a mobile operator. Proof, not slides. Teams Direct Routing, multi-tenant SIP borders hardened and held in production. The kind of mission where a profile is judged on what runs, not on what it promises.

The first client who opened the door

A mature idea is not enough. Someone has to bet on it.

That someone was my first client. After seeing the work delivered, they agreed to trust the next stage not to a large firm, but to mine: a sole proprietorship, one person, a proper B2B consulting contract. Two workstreams in parallel, UCaaS and Teams Direct Routing, from scoping to production.

That is a real bet, and I do not take it lightly. What they were buying was continuity: the person who designed the work would be the person who delivered the next stage, with no relay and no dilution.

Convincing, here, was not a sales pitch. The work already delivered did the convincing. But the decision to turn that trust into a company was mine. A serious first client is exactly the opening I had been waiting years to take.

Building the structure

Founding qaryon, in concrete terms, is a set of precise acts:

• A sole proprietorship in France, in the Grand Est. The return home was part of the plan.
• A full B2B contract kit: master agreement, annexes, NDA.
• Invoicing and quotes handed off to a tool, so they do not eat my weeks.
• A site, a technical journal, a brand.

I started as a sole proprietor, not a company. The simplest way to begin, ready to change the structure once the business demands it. You optimize the framework when it makes money, not before.

The rest is the price of the leap. No payslip that lands on its own, no team behind me to absorb a gap. Everything rests on what I deliver. That is exactly what I was after.

The same hand designs and deploys

qaryon exists to hold both ends. The person who draws the architecture also configures the SBC, tests the SIP flows, validates the QoS. No handoff to a junior.

This is not a slogan, it is a way of working. When I bring up a trunk, I write the config myself, I test it, I do not delegate it. One example, the config of a Teams Direct Routing trunk, where the detail decides whether the audio holds:

# SBC Teams Direct Routing: OPTIONS keep-alive + fixed codec on the trunk side
ProxySet 1
  ProxyName            = "sip.pstnhub.microsoft.com"
  ProxyEnableKeepAlive = 1     ; OPTIONS every 60s, or Teams drops the trunk
  KeepAliveTime        = 60
CodersGroup 0
  0 = g711Alaw64k, ptime=20    ; no SILK on the trunk side, ptime pinned to 20 ms

Two settings, two operational decisions. The OPTIONS keep-alive, without which Teams drops the trunk after a minute. The codec and ptime pinned, without which the audio degrades and tones come through wrong. Nothing spectacular at design time, it all plays out in production. That is exactly what a handoff to a junior loses.

What it opens

A first client opens the door, it does not close the subject. What comes next is more clients, this journal, and a SaaS platform I build in the background. The idea I carried for years is finally a company. It is a beginning, not a finish line.

If you are an integrator, a carrier, or a B2B team with a voice, UCaaS, or SBC topic to scope, the entry point is simple: get in touch.