One credit balance across every Built for Devs tool.

See the price before every paid action.

Credits

How credits work

  1. One credit equals one dollar for top-ups

    Top-ups are priced at a simple one-to-one rate.
  2. Subscriptions include more credits than the monthly price

    Choose a subscription for recurring work and receive the confirmed monthly credit allowance.
  3. Every tool uses the same balance

    Use credits for enrichment, evaluations, interviews, positioning, messaging, documentation, content, channel data, and eligible add-ons.
  4. Paid work runs on demand

    Nothing runs on a schedule. Nothing spends credits in the background without an explicit action.
  5. Set a spend limit

    Account-level limits prevent an API, CLI, or connected assistant from consuming more than the amount the company permits.

Plans

Subscribe for a monthly balance and add more when a larger project needs them.

Pro

[TBD]per month

For founders and small teams running focused research and GTM projects.

  • [TBD] credits per month
Choose Pro

Growth

[TBD]per month

For teams using multiple tools across ongoing product, research, and GTM work.

  • [TBD] credits per month
Choose Growth

Scale

[TBD]per month

For companies running higher-volume enrichment, research, evaluations, and deliverables.

  • [TBD] credits per month
Choose Scale

Services

Expert help

01

Expert review

Eligible messaging, documentation, and content deliverables can receive a paid expert review.

02

Reviewed positioning

The reviewed positioning tier is a fixed-fee service outside the shared credit balance.

03

Developer GTM Strategy

The complete team-led service is scoped separately from tool credits.

FAQ

Can an automated workflow spend the entire balance?
Set an account-level spend limit to bound automated usage.
Are subscriptions tied to one tool?
No. The monthly credit balance is shared across every eligible Built for Devs tool.

Pay for the work you run—not a separate subscription for every tool.