home

Digital products.

Digital products, small and large: from one tool to a full SaaS platform, and everything in between.

Some problems need more than pages. It might be one tool your staff opens every morning, a portal thousands of people sign in to, an app on their desktop or phone, or a SaaS platform you sell. We design it around the people who use it, build it on the right stack for the job, and make it secure, fast and accessible from the first screen. The team that designs it builds it, and we’re there to look after it when you need us.

Start a product

What you get

  1. Web apps

    Tools that run in the browser, from one internal app to a full product.

  2. SaaS platforms

    Products you sell: accounts, plans and billing, roles and permissions, and the admin behind them.

  3. Native and desktop apps

    Software for Mac, Windows, iOS or Android when the browser isn’t enough.

  4. Portals and accounts

    Members, students, patients or partners sign in and find what’s theirs.

  5. Registration, forms and payments

    Sign-ups, applications, bookings and checkout, with payments through Stripe or Authorize.Net, short enough to finish on a phone.

  6. Dashboards and internal tools

    The numbers and workflows your team relies on, pulled from the systems that hold them.

  7. APIs and integrations

    Connections to the CRM, payment, program and data systems you already run, and APIs of your own for others to build on.

  8. AI features

    Search, summaries, drafting and automation built into the product where they save people time.

Go deeper

What goes into an app.

On a digital product, these run together from the first sprint. Some have a page of their own.

  1. Modern frameworks, API development and the custom integrations that connect your systems.

  2. Flows and interfaces prototyped and tested with the people who’ll use them, before anything is polished.

  3. Built to WCAG and tested with assistive technology, so every person who has to use the app can.

  4. Security

    Sign-in, roles and permissions, encrypted data, dependency updates and security reviews, built in from the start, not bolted on.

  5. Performance

    Fast first loads and fast screens under real data, measured before launch and watched after it.

  6. Scalability

    Architecture, databases and hosting chosen for where you’re headed, so growing from a hundred users to a hundred thousand doesn’t mean a rebuild.

  7. Testing and reliability

    Automated tests, staged releases and monitoring, so updates ship without surprises.

How we work

Four phases, the same team.

  1. Discovery

    We watch how the work happens today — who signs in, what they need, where they get stuck — and map every system the app has to talk to.

  2. Design

    Flows and screens, prototyped and tested with the people who’ll use them before anything is polished.

  3. Development

    The team that designed it builds it, on Next.js and the systems you already run, with accessibility and security checked as we go.

  4. Delivery

    Documentation, training and monitoring, then support and improvements as the people using it ask for more.

Who it’s for

For the people who sign in every day.

  1. We can connect registration and resident services to the systems you already run, like RecTrac.

  2. We can build grant applications, member services and event registration.

  3. Libraries, scholarships and universities: we can build the search, applications and accounts people sign in for.

  4. Clear paths into patient portals like MyChart.

  5. Age verification, memberships and storefronts.

  6. Products and the tools behind them. We build our own, too.

How a project runs

It’s a loop,
not a line.

After launch we measure, learn and start again.
We don’t launch and disappear.

  1. Discovery
  2. Design
  3. Development
  4. Delivery

Launch is the start.

In a school library, a teacher and a child read together on a braille display.

Related work

Louis Library.

We migrated Louis Library from WordPress to a modern Next.js environment hosted on Vercel, giving users a faster, more seamless way to discover their next great read.

Read the story →

More app work

Built, shipped and still running.

  1. Our own product: an alt text generator on Next.js and Supabase that writes descriptive alt text for every image.

  2. A library of 297 responsive React and Tailwind blocks for P1, shipped as copy-paste components and Puck blocks with a live editor.

  3. A cinematic Next.js launch site with age verification, the Story Society membership and a shareable storyteller hub.

See all work →

Questions

  • If people only need to read and find things, a website. If they sign in, submit something or come back to see what’s theirs, an app. Plenty of projects are both, and one team can build both.

  • If it has an API and documentation, yes. We connect products to CRMs, payment processors, program and registration systems like RecTrac, and the data your team already keeps. Mapping every system the product has to talk to is part of discovery. If one has no API, we’ll tell you early and find the next best route, such as scheduled exports or a secure file sync.

  • We design and build to WCAG from the first screen and test with assistive technology before launch.

  • Yes. We plan for growth in discovery: the architecture, database and hosting are chosen for where you expect to be, not just launch day, so adding users, features or customers doesn’t mean starting over.

  • We do, whenever you need us: hosting on SOC 2–compliant platforms, monitoring, support and improvements.

Tell us who has to use it.

Start with the people and the task. We’ll bring the questions.

Start a product

Start a projectLouisville, Kentucky · Monday to Friday, 9 to 5

Tell us what
isn’t working.

No pitch deck. Just an honest conversation.Rather talk? Call 502.653.5977