The Next Admin Won’t Save Your Product: Build for Multiple Regulatory Futures Now

Regulatory uncertainty is not just a legal problem, it is a product problem, and it is already in your funnel. If you are a fintech PM, your roadmap is either pricing in ambiguity or pretending it does not exist. In this post I lay out a practical way to ship anyway: how to map uncertainty to user value, design configurable compliance, set up a regulatory radar, and choose bets that do not get zeroed out by one enforcement memo. If you have ever watched a launch die in review, lost weeks to "we will know after we hear back", or built something you cannot confidently sell, expand the post. This is a playbook, not a lament.

Regulatory uncertainty is the kind of fog that does not just slow you down, it quietly rewires what your team believes is possible. A strict rule can be painful, but at least it is a map. Fog is worse because it turns every decision into a wager, and the cost of being wrong is not a bug, it is an existential event.

I learned that the hard way at Bullish.

Bullish was not some hoodie-and-Discord shop. It was 2022, and we were building a world-class crypto exchange with world-class market-structure leadership. The company was (and is) led by a fantastic CEO, Tom Farley, former president of the New York Stock Exchange Group. We were on the path to going public via a SPAC transaction with Far Peak Acquisition Corp. Inside the building, it felt like we were doing everything "the right way". Dotted every i, crossed every t, compliance embedded, process documented, controls tightened. We were not asking for permission to be reckless. We were trying to be legible to the system.

And for a moment, it looked like it was going to work.

We were told, by lawyers on both sides, ours and the SEC’s orbit, that approval was imminent. The narrative had shifted from "if" to "when." The parties were planned. The champagne was on ice. We were hours away from the announcement.

Then FTX collapsed.

If you were in crypto at the time, you remember the sick feeling in your stomach as the headlines rolled in and the withdrawal rumors hardened into a bankruptcy filing on November 11, 2022. Overnight, the entire industry got re-labeled. Nuance died. The distinction between firms that tried to build with institutional discipline and firms that played fast and loose stopped mattering to outsiders. The fog thickened into something worse: guilt by proximity.

And then the second-order effects hit. Deals that had been feasible became politically radioactive. Risk committees went into lockdown. Partners tightened. Conversations slowed. The Bullish SPAC was ultimately called off in late December 2022. A month after the collapse, I was laid off.

That experience burned one lesson into my brain for fintech product managers: regulatory uncertainty is not a legal problem parked in another department. It is a core product constraint that can vaporize months of execution in a single news cycle.

The fintech PM translation: value is granted, not inherent

No product has intrinsic value. Value is granted by customers when your product solves a real problem in a way they can trust, adopt, and keep using. In fintech, trust is inseparable from legality, bankability, and survivability. When the rules are murky or shifting, customers cannot tell what is safe to adopt, partners cannot tell what they are allowed to support, and your team cannot tell whether the next quarter’s work will become tomorrow’s liability.

So uncertainty does not merely "block innovation." It corrupts discovery. It breaks the feedback loop that tells you what customers actually need and what they will pay for. You cannot interpret adoption signals cleanly when users are hesitating because they are unsure whether your product will still exist, or whether they will get de-banked, audited, frozen, or embarrassed. Innovation dies not only from prohibition, but from hesitation.

From a fintech PM seat, the last five years have taught a brutal lesson: you can build the right thing and still lose if the regulatory narrative turns against you. Crypto and digital assets are the loudest example, but the same fog pattern shows up in BNPL, earned wage access, open banking, data aggregators, AI underwriting, and even the humble act of moving money across borders.

So let us get practical, because you are not paid to observe storms. You are paid to ship in weather.

The playbook: how fintech PMs ship through fog

1) Treat regulatory ambiguity like a first-class product surface

Stop relegating compliance to a gate at the end. Build a "policy layer" into your product thinking the same way you build pricing, risk, and identity layers.

Actionable move: Create a one-page "Regulatory Assumptions" doc for every major initiative:

• What we assume is permitted today (with a confidence score 1 to 5)
• What would break this product (2 to 3 interpretations that kill it)
• What we will do if that happens (fallback flows, feature flags, partner swaps, comms plan)

This turns uncertainty into explicit inputs. It also changes how you argue internally. Instead of "legal says no," it becomes "we are at 2 out of 5 confidence on this assumption, so we either buy down risk or we scope accordingly."

2) Build configurable compliance, not one-off compliance

If your compliance posture is hard-coded, every policy shift becomes a rewrite. If it is configurable, it becomes a settings change and a comms update.

Actionable move: Invest in feature flags and policy rules for:

• jurisdiction gating (state-by-state toggles)
• KYC/KYB tiers (lightweight to enhanced)
• transaction limits and velocity controls
• disclosures and consent flows
• product eligibility rules (who can use what, when)
• asset availability (listings) and restrictions

This is not glamorous work. It is the difference between "we are shutting down this feature" and "we are adjusting the policy and continuing to serve customers."

3) Redesign experimentation so it survives enforcement mood swings

Classic growth experimentation assumes your experiments fail only for product reasons. In fintech, experiments fail because sponsor banks get nervous, processors change policy, compliance reinterprets risk, or headlines spook users.

Actionable move: Maintain two experiment backlogs:

• Value hypothesis tests: does the user want this?
• Viability hypothesis tests: can we deliver this legally and sustainably?

Track both. A feature that converts but cannot survive viability is not a win, it is debt. Run viability tests early with counsel, bank sponsor, and critical partners in the same loop.

4) Make your partner strategy anti-fragile

In fintech, your product is only as resilient as your most conservative partner.

Actionable move: For every mission-critical dependency (bank sponsor, issuer, custodian, processor, liquidity provider, identity vendor), maintain:

• a primary and secondary option
• a migration playbook with realistic timelines
• contract awareness (termination triggers, policy-change clauses, notice periods)

When the fog thickens, your ability to switch partners is sometimes the only thing that keeps you alive.

5) Convert uncertainty into customer trust signals

Customers do not want your policy analysis. They want confidence: "Will this still work next month? Will my funds be safe? Will I get locked out?"

Actionable move: Ship trust primitives:

• clear status pages for transfers, holds, and withdrawals
• transparent disclosures written like a PM, not like counsel
• support escalation paths for compliance-related issues
• proactive comms when policy changes affect users

Trust is part of the product, not marketing.

6) Build a regulatory radar that outputs decisions, not trivia

Most teams either ignore policy until it hits them, or drown in newsletters nobody reads.

Actionable move: Run a monthly 45-minute "Regulatory Radar" with a fixed output:

• Top 5 developments to watch (not 50)
• Which product surfaces they touch
• Which assumptions doc entries change
• Which experiments buy down risk next

Tie it to roadmap choices, partner strategy, and user messaging. If it does not change decisions, it is noise.

January 2025 gut feel: what to keep your eyes on

If you are writing strategy for 2025, assume the fight shifts from "can this exist" to "under what conditions can this scale." My predictions and things I would keep eyes on:

• Stablecoins as payments infrastructure: whether regulators and bank partners converge on stablecoin-backed settlement as legitimate rails, or keep treating it as a suspicious cousin of securities markets.
• Custody, commingling, and responsibility: stricter expectations around segregation, disclosures, and who bears responsibility in the stack. Post-FTX, nobody gets benefit of the doubt. ([AP News][3])
• Fintech-bank partnership scrutiny: increased pressure on BSA/AML programs, marketing claims, complaint management, and operational resilience.
• Open banking moving from "data access" to "liability and consent": privacy, authorization, and responsibility allocation become product requirements.
• AI underwriting and fraud as a compliance surface: explainability, monitoring, and governance move from "model excellence" to "can we defend this to a regulator or a partner risk committee."

None of this means "do not build." It means build like you intend to stay alive.

The hopeful part, and the hard part

A new administration can change tone, priorities, and leadership, and that matters. But do not outsource your product survival to politics.

The real opportunity for fintech PMs is to build products that remain viable across multiple regulatory futures. That is what I wish more of crypto had internalized before the FTX moment forced everyone to learn it at once.

We need clearer rules, because clear rules let builders compete on serving customers rather than on guessing what mood the system is in. But until clarity arrives, create local clarity inside your company: explicit assumptions, configurable compliance, resilient partners, and experiments that test viability as seriously as value.

Break through the fog and you unlock the real prize: a new wave of financial products that customers can trust, partners can support, and teams can iterate on without waking up to find the ground gone.

If you want, I can also:

• punch this up further into a tighter narrative arc (cold open with the "champagne on ice" scene, then zoom out),
• or format it like a paywalled post with headers, bold callouts, and a "PM checklist" box at the end.