About

We built Clarity because software shouldn’t be scarce.

Organizations have always had more software needs than they could afford to solve. The people closest to the work often knew exactly what would make it better - but building the software required engineering resources, time and budget most ideas could never justify.

Generative AI changed what was possible.

Clarity is our attempt to put that capability in their hands.

Operating since
2014
Engineering
US-based
Technology
Patent-pending
SOC 2 Type 1
Audit underway
Where Clarity came from

We used to build the software.

For more than a decade, we built software for organizations. Clarity is what happened when generative AI gave us the opportunity to turn that experience into a Platform the people closest to the business could use themselves.

The decade before
  • We built production software.
  • We solved operational problems.
  • We modernized systems people could not replace.
  • We built products of our own.
  • We lived the economics and the limits of traditional software development directly, on every project.
What it taught us
  • Useful software ideas are everywhere.
  • Engineering capacity is always limited.
  • Many worthwhile problems never justify a traditional project.
  • Organizations tolerate spreadsheets, manual processes, aging systems and oversized SaaS because custom software historically cost too much.

We built Clarity so the people who understand the business can increasingly build it themselves.

How we got here

A decade of building, and then the economics changed.

  1. 2014

    The practice begins.

    A small senior team building production software for organizations. Operational systems, products, modernization work.

  2. A decade

    Real systems, real constraints.

    Healthcare, logistics and hourly workforces. Software people depended on, with the economics of traditional development attached to every project.

  3. Generative AI

    The arithmetic changes.

    For the first time, the cost of turning a described business need into working software moved - and moved by enough to matter.

  4. Clarity

    The Platform.

    One Platform that creates, deploys and manages software across many projects, designed for operators rather than developers.

What the work taught us

The work that taught us why Clarity needed to exist.

These are real production systems, and they are not here to prove we can be hired to build the next one. They are here because each of them taught us something the Platform is a direct response to.

  1. Ramble

    The first multi-modal communication button on a website, built in the early days of WebRTC. One script tag on a page. Acquired in 2020.

    What it taught us

    Writing the feature was never the hard part. Browsers, networks, support and years of production operation were. It is why Clarity treats deployment and lifecycle management as part of the product rather than as what happens after the product.

  2. A full electronic medical record

    The complete EMR for a multi-facility skilled nursing aggregator. Not a module bolted onto somebody else's system. The record itself, across every facility.

    What it taught us

    Almost everything we needed to know lived with the nurses and administrators rather than with us. Months went into translating it into something buildable. The translation was the project, and it is exactly the layer Clarity exists to collapse.

  3. Hourly workforce systems

    A job service and app for hourly workers, where the operational reality is high turnover, thin margins and people who will not tolerate bad software.

    What it taught us

    Everyone could see improvements worth making. Each one had to beat everything else in the queue for budget and most never did. Not because they were bad ideas, but because a traditional project could not be justified for them.

Plus dozens of others since 2014. The through line was never a technology. It was the kind of problem: the operational software an organization actually runs on, in industries where getting it wrong is expensive.

Much of the software created with Clarity runs inside organizations that do not want their internal systems used as marketing material. We respect that.

The insight behind Clarity

The person who understands the problem should be able to drive the solution.

Traditional software development puts a translation layer between two people: the one who understands the business, and the one who knows how to create the software. Every requirement has to pass through it. Context gets lost on the way, and the cost of that translation is paid again on every project.

Clarity exists to collapse much of that layer. Not to remove the expertise, but to stop making it the bottleneck between a problem somebody can see and the software that would solve it.

This is not an argument that everyone should become a developer. We do not believe that, and we are not building for it.

The operator should not have to become a developer. The technology should become capable of carrying more of the developer’s burden.

The complexity belongs to Clarity, not the user.

What we believe

Things you can hold us to.

  1. We say no when it isn't a fit.

    Clarity is not the right answer to every software problem. If something off the shelf does the job, buy it. We would rather say that early than force the Platform into a situation where another approach makes more sense.

  2. We tell you where things actually stand.

    Product maturity, security posture, roadmap, limitations. You will read the gaps here before you hear them in a meeting, and we do not describe things we intend to build as things we have built.

  3. We make the economics understandable.

    What the Platform costs and how the operating models differ are published. Nobody should have to sit through an opaque process to work out the shape of the deal.

  4. What you build stays yours.

    Organization-specific applications, generated source and your business data belong to you. Environments stay isolated, and you keep portability and control whether Clarity runs inside infrastructure you govern or in a dedicated environment we operate for you.

The team

Small by design.

Clarity is built by a senior software team with experience across startups, enterprise systems and production software. We stay small intentionally, because the Platform is supposed to carry more of the technical burden over time - not because we plan to scale by adding armies of consultants.

That is also the test of whether the thing works. If the Platform needs a large services organization standing behind it to be useful, we have not finished building it.

The company

The things worth knowing.

Operating since
2014
Engineering
US-based
Prior products
Ramble, acquired 2020
Technology
Patent-pending
Security
SOC 2 Type 1 audit underway
Entity
Clarity AI is the operating brand of Codewerx LLC

On security specifically: Clarity AI is currently undergoing its SOC 2 Type 1 examination, which assesses how our controls are designed. It is underway and no report has been issued yet, and we will not imply otherwise. A SOC 2 Type 2 examination, which assesses how those controls operate over a period of time, is planned to follow. The longer-form control framework is available under NDA.

Useful software should not be limited by who has access to an engineering team.

That is why we built Clarity. If your organization needs more software than it can currently produce, that gap is the thing the Platform was built for.