Jordan Pavelich

Product manager with 9+ years building platforms in fintech and proptech, at start-up and enterprise scale - mostly in risk, credit, payments and workplace data.

Approach

Start with the problem. Who has it, why it matters and why now. Getting that clear first makes everything after it easier, and the riskiest assumptions get tested cheaply before anything is built.

Keep discovery going. Regular conversations with customers and the teams that support them (customer success, risk, sales), not just at the start of a project. The best ones turn up something unexpected that changes the plan.

Build the platform once. Shared rules live in the core, and each customer, brand or partner gets its own configuration on top. Buy what's already standard and save the build for what makes the product different.

Bring legal, compliance and risk in early. In regulated products they shape the solution, so they're part of the product process from day one. Done that way, launches usually ship faster.

Pick one outcome to move. Each initiative gets one outcome metric, a few leading indicators and guardrails to catch side effects.

Keep specs short and explain the why. Lean specs give the team direction and the reasoning behind it, so engineers can make good trade-offs on their own.

Use AI where it saves time. AI workflows for research, discovery and prototyping shorten product cycles, and work best shared as templates across teams. Judgment and the final call stay with people.