Why we ship every week — the cadence commitment

Software for working card dealers has a specific failure mode: the tool you depend on goes quiet. The release notes stop landing. The Discord goes silent. The "we're working on it" reply to a feature request becomes a "we'll look at it." Six months later, you're still on the same version, still working around the same bugs, still wondering if the company is still alive.

I've been on the customer side of that. So has every working dealer reading this. The commitment in this post is the antidote.

The commitment

The vault ships a meaningful update every week.

By "meaningful" I mean: visible to a user, documented on the changelog, traceable in the codebase. Not always a headline feature — sometimes it's a workflow fix, an integration polish, a Pokemon-set catalog refresh. But something real, every week, with the date and the explanation public.

The current cadence (as of mid-2026): roughly 4-6 changelog-worthy releases per month, averaging one per week. The first releases were rolled up retroactively; from May 2026 forward, expect them weekly.

What "every week" actually means

Three categories of weekly release:

1. Feature (40% of weeks)

A user-visible new capability. Custom title-template variables. A new channel integration. Multi-region eBay. The kind of thing that gets a paragraph on the changelog and changes how you work.

2. Improvement (40% of weeks)

An existing capability that got better. Faster identify pipeline. Better Pokemon-set catalog coverage. Tighter UI ergonomics. Improved cross-channel conflict detection. Sometimes the most valuable releases — they don't get marketing headlines but they make every existing user faster.

3. Operational note (20% of weeks)

Plumbing changes, infrastructure improvements, support process changes. These don't always change what you see on screen, but they make the system more reliable.

What the cadence costs

Honest answer:

• Engineering hours: ~30 per week sustained. This is most of my development time. Other things — bug fixes, customer support, the dealer-store itself — get squeezed.
• Documentation time: ~2-3 hours per week writing changelog entries and updating affected /help articles.
• Quality risk: shipping weekly with one person means bugs occasionally land. The mitigation is automated tests covering the listing-write paths (the parts where a bug costs the dealer money). Other surfaces sometimes ship with rough edges that get cleaned up in the following week.
• Roadmap discipline: I can't get distracted by every new idea. The roadmap is committed to 4-6 weeks out; new requests get triaged into "doing this quarter" or "doing next quarter" buckets. No exceptions.

What the cadence costs you

This is also honest:

• Occasional bugs. When something ships every week, occasionally the thing that shipped is slightly broken. I fix within 24-48 hours and write the fix into the next changelog.
• Workflow churn. A UI improvement may move a button. You'll notice. Within a week you'll be used to it.
• Information overload (rare). Reading the changelog every week is optional. If you'd rather just see the headlines, the monthly newsletter pulls the top 3-5 changes.

Why this cadence is worth it

Three reasons.

Reason 1 — You can plan around it

If you know the vault ships every week, you can plan around it. A bug report you file today is on the list this week, next week at the latest. A feature request lands on the roadmap or in the "not doing" pile within a week. There's no six-month silence.

CardDealerPro's cadence is roughly quarterly (their CDP 2.0 release was their biggest in a year-plus). CardLuma is similar to mine — they ship every 2 weeks, sometimes faster. The cadence is a real differentiator vs CDP.

Reason 2 — The product improves visibly

Most software gets worse over time. Features pile on, technical debt accumulates, performance degrades. Weekly shipping forces the opposite — every week is an opportunity to improve, and the changelog makes the improvement public.

The vault is materially faster, cleaner, and more capable than it was six months ago. Six months from now it will be materially better than today. The changelog is the receipt.

Reason 3 — The trust accumulates

Every dealer I know has been burned by software that went silent. The cumulative cost — switching tools, re-learning workflows, migrating inventory data — is high. The trust premium for a tool that visibly ships is real.

I'd rather earn that trust than try to talk you into it.

The "but what about big features" question

Reasonable objection: a weekly cadence rewards small features and punishes big ones. Major releases (e.g., Whatnot integration, multi-region eBay) take months to build; they don't fit into a one-week chunk.

The answer: big features ship in stages. The eBay integration shipped in dozens of distinct changelog entries over months — OAuth, listing-builder, business policies, label printing, multi-region support, item-specifics, etc. Each entry was real progress visible to users. The "complete" eBay integration wasn't a single big-bang release; it was a continuous build that users could watch unfold. The same staging pattern is how the Phase 5 channels (TCGPlayer, Whatnot, CollX, Shopify) will land.

This pattern is the same one used at every well-run software company. Stripe, Linear, Vercel, Tailscale — none of them announce three-month epics as single releases. They ship in pieces, document each piece, and let the pieces compound.

What you can do about it

• Read the changelog. Every release, every meaningful improvement, public.
• Email me. Feature requests, bug reports, "I wish this did X." I read every message.
• Sit on a tool that visibly improves. That's the actual deliverable.

The negative case

To be fair to the alternative argument: weekly shipping is also a cost for some users. Specifically:

• Users who hate change. If you want the software to stay the same as the day you signed up, weekly cadence is the opposite of what you want.
• Enterprise customers with change-management workflows. We don't have these (the vault is built for individual dealers, not enterprises), but if a feature you depend on changes, you have to know.
• Users who rely on bug behavior as feature behavior. If your workflow depended on a bug being there, fixing the bug is also "breaking" your workflow.

I accept these costs. The trade is worth it.

Closing

A weekly release cadence isn't a marketing claim. It's an operational commitment. The changelog is the receipt; check it any week and you can verify.

If the cadence ever stops being weekly, it'll be because something changed materially — either a sustained engineering issue, a deliberate strategic shift, or a founder situation. I'll write that post when it happens. As of mid-2026, neither has happened, and I don't see one coming.

— Jamie

Public changelog: /changelog. Read it; verify the claim.