Six roles, and one application

What you would own

• The rule engine and its decision API — correctness here is the product
• Card issuing integration once the BIN sponsorship lands
• The call on what gets built and what gets bought
• The engineering standard, because you will hire against it

What we need

• You have run payments, ledgers or authorization systems before
• You have been the person accountable when money moved incorrectly
• You hold correctness and shipping speed at once
• You are comfortable with no team and no process yet

What you would own

• Rule evaluation — sixteen kinds today, every one running on every purchase
• The public decision API, which has to be fast and has to be right
• The sandbox: four ways to build one rulebook, all on the real engine
• Webhooks, ledgers and reconciliation

What we need

• Strong backend engineering where being wrong costs money
• You write the test before the clever refactor
• You can find the bug that only appears on the sixteenth rule
• Payments experience is a bonus, not a requirement

What you would own

• Ship across the engine, the API and the front end
• Own things end to end — build it, deploy it, watch it, fix it
• Talk to the people using it, because there is nobody in between
• Notice what is broken and fix it without being asked

What we need

• You have shipped something real that people used
• You would rather learn four things well than one thing perfectly
• You are comfortable with ambiguity, because most of this is ambiguous
• You have worked somewhere small, or you want to

What you would own

• Add rule kinds to the engine and write the tests that prove them
• Improve the sandbox — every one of its four modes has rough edges
• Write documentation for an API that is still forming
• Break things on purpose and report what broke

What we need

• You can write code and read code you did not write
• You ask when you are stuck instead of disappearing for three days
• You are curious about payments, or willing to become so

What you would own

• Draft and ship posts on LinkedIn and X
• Find the places people describe this problem in their own words
• Turn the product into things people can see — demos, recordings, comparisons
• Watch what works, because we now have the analytics to tell

What we need

• You write clearly. This matters more than any tool you know.
• You have built an audience for something, even a small one
• You would rather ship ten rough posts than plan one perfect campaign

What you would own

• Find companies handing spending authority to software and start real conversations
• Reserved places in the first cohort — $50 covers your first month when issuing opens and locks $199/mo for your first 12 months
• Bring back what people actually say, including where we are wrong
• The first repeatable version of how this gets sold

What we need

• You have sold something technical to technical buyers
• You are comfortable saying “not yet” about issuing
• You can start from nothing: no inbound, no list, no brand
• You would rather have twenty real conversations than two hundred sends