About OrsaNova

OrsaNova was founded on a simple principle: real-world experience beats vendor promises. We spent two decades building, operating, and scaling communications businesses on NetSapiens, 3CX, and FreePBX — which is where we learned how much of the work gets shaped around software that almost fits.

That is the gap we build into. Today we develop custom software across industries: mobile applications, web applications and browser extensions, and custom systems that reach hardware and the tools a team already runs. Unified communications is where our depth started; cannabis is where we work with data that demands stricter handling than most; and a good deal of our work belongs to no category at all.

The name "OrsaNova" means "new bear" in Italian, reflecting our founder's heritage and our brand philosophy. Like the bear, we're protective of the people we work with, strong in our convictions, and reliable when you need us most.

We've Operated, Not Just Built

Two decades running communications businesses on NetSapiens, 3CX, and FreePBX means we have been the ones living with the software after it ships — the billing edge case at month end, the migration that cannot drop a call, the workaround that quietly becomes the process. We scope from that side of it.

We Ship Our Own Products

We build and maintain our own software, not only client work: a local-first mobile app with on-device analytics and store-native billing, a browser extension integrating four business systems, and a desktop plugin driving Bluetooth hardware. Techniques get proven there first, on software we have to live with ourselves.

Built To Be Owned

Documented, tested, and handed over in a state your team or ours can maintain. No deliberate lock-in, and no dependency on us that we engineered on purpose.

To build the software our clients can't buy. Everything we do — how we scope, what we ship, and what we hand over — is judged against one question: does this actually fit how the work gets done?

That means understanding the process before writing code, shipping in increments so direction can change cheaply, and handing over something documented and testable that your team or ours can maintain. No deliberate lock-in, and no software that has to be worked around.

Operators Who Build

We are a small, founder-led team. The person who scopes your project is the person who writes the code — there is no layer between the conversation and the build.

Our background is in running communications businesses, not only writing software for them. That shapes the questions we ask first:

• What does this process actually look like today, including the workarounds?
• What breaks at month end, at scale, or when someone is offline?
• Who maintains this in two years, and what do they need from us to do it?
• What is the least data this can collect and still work?

Where We Go Deep

Unified communications, where our operating experience is. Cannabis, where we work with data that demands stricter handling than most. And a good deal of work that belongs to no category at all.

Say the Real Thing

If a project is the wrong idea, or we are the wrong people for it, we say so before you spend money finding out. We would rather lose the work than take it knowing it will not land.

Privacy Is a Default, Not a Feature

Least data, least privilege, and no quiet collection. Our own products are local-first with cloud sync opt-in, and the commitments in our privacy policy are the ceiling for everything we build, including for clients.

Finish the Job

Software that is 90% done is not done. That includes the documentation, the tests, and the handover.

Stay Small Enough to Care

We take on work we can give real attention to. You talk to the people building your software, not to an account layer in front of them.