Get the technical work right for your company’s next stage of growth.

We work alongside your team to resolve the technical decisions holding up a launch, rebuild, or expansion, and build the software to move it forward.

See the work ↓

You know what needs to work better. Where do you start?

Customers are asking for something your product doesn't do yet. A prototype is ready for its first real users. Or your team keeps rebuilding the same spreadsheet to get through the week.

Before adding more software, we look at what you already have. We work through what to keep, what needs to change, and which part is worth building first. Then we take responsibility for that work alongside your team.

It started with an accountant who wanted to build a product.

Karen Webber knew forensic accounting. She needed someone who could understand that work and turn it into software. Chase joined as FraudFindr's initial technical partner and wrote its first lines of code.

As the product grew, the work expanded to enterprise security and building an engineering team. FraudFindr reached seven figures a year, and in 2023 it became part of The Bonadio Group through the acquisition of Webber CPA.

The relationship continued after the acquisition. Chase worked with Bonadio's team to bring FraudFindr into the firm, then helped build CareFindr from scratch for county foster-care departments.

Other clients brought us different kinds of work.

Browse the client work and partnerships

Find the work that looks like yours.

Start with the project in front of you. You can see how we approach it and read about related client work.

We agree on the first piece of work before we start.

You can come to the first conversation with a problem, an idea, or a project that's already underway. We'll talk about what you need and where we can help.

  1. 01

    We recommend an approach you can question.

    We review the relevant systems and explain the tradeoffs before agreeing on a first scope. For AI projects that need investigation, our $5,000, two-week AI Audit gives you a blueprint and a dated 12-month roadmap you can take to any team.

    See what's in the AI Audit
  2. 02

    You see the software take shape as we build.

    We agree on scope and price before building. The code lives in your repository, and you review working versions as we go. Your engineers stay involved in decisions that affect the systems they own.

  3. 03

    Your team can take over, or we can stay involved.

    We document how to run the software and walk your team through it. If you need ongoing development or support, we agree on that scope separately. You know who is responsible after launch.

Chase Poirier, founder and technical partner at TheShop

Hi, I'm Chase.

I've spent ten years building software with founders and engineering teams. Some projects started with an idea on paper. Others meant joining a team that already had customers depending on the product.

I like getting far enough into a business to understand why something needs to be built. That's how I worked with Karen, and it's how I want to work with you.

You'll work directly with me on the technical decisions and the build. When we need another engineer, I bring in someone I've worked with and stay responsible for the project.

More about the work I've done

A few things you may want to know.

Does the project need to involve AI?

No. We also build applications, websites, and integrations that don’t use AI. We choose the tools once we understand what the software needs to do.

Can you work with our engineers?

Yes. We agree on which work we own and which decisions need their input. They stay involved in changes to the product while continuing the work already on their plate.

Do we have to start with an audit?

We can scope a clear build directly. A paid diagnostic is for the questions we need to answer before we can recommend an approach or price the work.

Can someone else maintain it?

We build in your repository and include documentation and a walkthrough in the handoff. We explain the technical choices so your team or another developer can continue the work.

Who owns the software?

For client builds, ownership is set out in the contract and the code lives in your repository. Creator partnerships have their own ownership agreements.

Tell us what you're trying to build.

Send a few sentences about the project and where you're stuck. We'll reply by email to arrange a conversation. You don't need a finished brief.