Staking RAIN tokens vs pay-as-you-go access
Both paths get you the same kind of thing from us: an agentic system that reads a situation, acts through real tools, and checks its own work without someone babysitting it. The difference is not what gets built, it is how you pay for the relationship. Staking RAIN tokens ties your access to holding a token position; pay-as-you-go keeps each engagement separate, scoped and paid for on its own terms.
By Precipitate · Updated 19 August 2026
| staking RAIN tokens | pay-as-you-go access | |
|---|---|---|
| What it costs you in effort | Staking means acquiring and locking RAIN tokens before the relationship starts, on top of whatever the engagement itself takes to scope. You end up holding a position in a token, not just paying for work, so someone on your side needs to be comfortable with that and with tracking it over time. | Pay-as-you-go asks for less upfront. You agree on the engagement, we scope it, and payment tracks the work directly. No token to acquire, hold, or think about afterward. |
| How fast it is to get running | We still map the manual work first and say plainly what we can and cannot own, so staking does not skip that step. What it adds is the token setup, done before or alongside that mapping. | Same mapping, same honesty about scope, but nothing to acquire first. For a single well-defined project this is usually the faster route to a signed scope and a start date. |
| How it handles the unusual case | Because the relationship is ongoing, the people who mapped your manual work in the first place are still around when something odd comes up, already holding the context to triage it without a re-briefing. | An unusual case gets handled if it falls inside what was scoped for that engagement. Outside that, it becomes a new conversation, and possibly a new engagement, before anyone touches it. |
| What happens when it breaks | Operating the system is part of what staking buys, so a break is something we are already watching for, the same way we watch our own production systems (we run 110-plus scheduled jobs across 40-plus integrations for ourselves, and treat a silent failure there as seriously as a loud one). | Fixing a break after an engagement has closed is new work, priced and scoped like anything else. If the engagement included a support window, it is covered inside that window and not past it. |
| What you own at the end | You own the system we built, same as with pay-as-you-go, but you also hold a token position whose value moves independently of whether the system keeps performing well. Some businesses want that alignment. Others would rather not carry it. | You own the system outright, full stop, with nothing tied to a token's price or liquidity. If we vanished tomorrow, what you own would not change. |
| When it stops making sense | Staking stops making sense for a business that needs one thing built once, has no appetite for holding any token, or is not ready to commit to an ongoing relationship with a small team. | Pay-as-you-go stops making sense once you are running several coordinated systems that need to keep talking to each other and be watched around the clock. At that point, discrete engagements start to feel like rebuilding the same context every time. |
Choose staking RAIN tokens if you want us operating your systems on an ongoing basis and you are comfortable holding a token position as part of that relationship.
Choose pay-as-you-go access if you need one system built and shipped, want ownership to stay simple, and are not ready for a standing relationship with us.
Related questions
Can we start with pay-as-you-go and move to staking later?
Yes. A discrete engagement does not lock you out of an ongoing relationship afterward, and plenty of businesses want to see one system working before committing further.
How do we know Precipitate can actually keep a system running unattended?
Look at what we run for ourselves, not what we claim for clients: more than 110 scheduled jobs across 40-plus live integrations, 88 systems in production, content shipped in seven languages. That is our own operation, not a client result, and it is the same discipline applied to what we build for you.
Not sure which side you are on? Tell us what the manual work is, and we will tell you honestly what a machine can take off your plate and what still needs a person.
One reply from a person, usually same day. No deck, no discovery call, no sales sequence.