PracticeWings is currently in beta. Request early access →

Built by a CPA Who Needed Better Software

Not by a tech company guessing what accountants need. By someone who lives this work every day.

I run a tax firm. I've used every practice management tool on the market — some for years, some for just long enough to realize they didn't understand how my firm actually operates.

Every platform I tried had the same fundamental problem: they were designed by software people, not practitioners. They'd build a task system that couldn't handle the simple fact that a review can't start until preparation is done. They'd offer a "client portal" that was really just a file upload widget. They'd charge extra for API access that should be table stakes.

So I started building the tool I wished existed. Not as a side project or a startup pitch — as a solution to real problems in my real practice. Every feature in PracticeWings comes from firsthand experience with actual clients, actual deadlines, and actual compliance requirements.

Why "By a CPA" Matters

These aren't theoretical benefits. They're specific design decisions that only come from doing this work.

Task Dependencies That Make Sense

Review can't start until prep is done. Partner sign-off requires completed review. In PracticeWings, these dependencies are built into the workflow engine — not managed with sticky notes and Slack messages.

Multi-Office from Day One

I manage staff across locations. PracticeWings was built with multi-office support as a core feature, not a bolt-on. Office-scoped visibility, cross-office assignments, and per-office reporting are fundamental.

Client Portal Doc Requests

Tired of chasing K-1s by email every year? The portal lets you send document requests that land in the right folder when clients respond. Stop the "did you get the W-2 I sent?" email chains.

Engagement Tiers

Not every 1040 is the same. A straightforward W-2 return is not the same as a client with three rental properties and an S-Corp. PracticeWings supports engagement templates and tiers because the work is different.

The Approach

Building transparently, with real practitioners involved, without rushing features or cutting corners to hit a launch date.

PracticeWings is being built in the open, with input from real firm owners and managers. We're not rushing to ship a half-built product. We're not pretending features exist when they don't. And we're not going to sell something we wouldn't use ourselves.

In fact, my own firm will be the first firm to use PracticeWings in production. If it's not good enough for us, it's not good enough for anyone.

Timeline

Summer 2026
Internal pilot — founder's own firm begins daily use of PracticeWings
Fall 2026
First external beta firms onboarded with direct founder support
2027
General availability with full support and onboarding

See It in Action

PracticeWings dashboard showing firm overview with tasks, time entries, and key metrics

The PracticeWings dashboard — built to give you a complete view of your firm at a glance.

Not a Prototype

The product is already built. The beta is about refinement, not development.

60+

API Modules

122

Data Models

90+

Web Pages

27

Settings Pages

Join the Beta

Help shape practice management software built by someone who does the same work you do.

Request Beta Access