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

I had the idea for qaryon long before I had the chance to start.

For years, I wanted my own structure so I could 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 mission to a one-person structure. That client came in Switzerland.

Leaving for Switzerland

Twelve years with telecom integrators and carriers, designing architectures others had to deploy, then straightening out drifting projects. My ground never moved: enterprise and carrier voice. UCaaS and CCaaS, SBC and IPBX, carrier interconnection, automation and provisioning. From those years I keep a stream of people and projects, each more impressive and more interesting than the last, and a few numbers: a UCaaS platform for a national group of 16,000+ users delivered in under six months, provisioning time cut from several hours to a few minutes per site, AI-boosted telephony solutions, and counterparts who kept getting more technical.

Those 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.

Switzerland was a telecom mission at a mobile operator. Concrete work, with several UCaaS solutions to put in place for a player making its first move into B2B. The kind of mission where someone is judged on what runs, not on what they promise.

The first client who opened the door

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

After seeing the preliminary work delivered and what I could do, my first client handed the next stage to my structure rather than another. A sole proprietorship, one person, a proper B2B consulting contract. Two workstreams in parallel, two solutions to wire into their systems and roll out to their own customers, from scoping to operations.

The work already delivered did the convincing, not a sales pitch. But the decision to turn that trust into a company was mine.

Building the structure

Founding qaryon is a set of precise acts:

• A sole proprietorship in France, in the Grand Est.
• A B2B contract kit: master agreement, annexes, NDA.
• Invoicing and quotes automated.
• A site, a technical journal, a brand.

I started as a sole proprietor, not a company, and the question of changing that status is already on the table.

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 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 equipment, tests the flows, validates that it works.

When I bring up a solution I do not delegate it, and I bring everything I have to finishing the installation. The detail is what 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.

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. It is a beginning, not a finish line.

A voice topic to scope, on the integrator, carrier, or B2B side? Get in touch.