pre.dev

Plan, build and verify software through a browser or terminal coding agent.

Freemium, credit-based subscriptions and custom enterprise plansDeveloper tools
Visit website
Reported revenue≈ $500,000ARR · Unspecified $500K ARR reported in the March 12, 2026 interview; exact financial cutoff unspecifiedOriginal disclosure
Business modelFreemium, credit-based subscriptions and custom enterprise plansDeveloper tools
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff

Business overview

Public positioning

A coding-agent platform that plans work, executes tasks and presents software changes for review. Official LinkedIn gives a 2-10 employee company-size range. A June 9, 2026 founder article describes two engineers, and an official company post identifies Adam Elkassas and Arjun Raj Jain as co-founders. Engineer count and founder count are not total staffing; the exact current payroll count is unverified.

How it makes money

Plans increase monthly credits and collaboration capacity. The current company also sells separately quoted RL tasks and codebase licences; those later offerings are not added to the historical income figure.

Business breakdown

Researched Oct 20, 2026

Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.

The customer problem

pre.dev offers a coding agent that plans work and produces changes through browser and terminal workflows. Editorial interpretation: its buyer is paying to reduce the coordination gap between a rough requirement and a reviewable implementation. This can be especially relevant for agencies repeating scoping work across projects. The commercial opportunity is stronger when the system helps a buyer reach an accepted result consistently, rather than merely generating a large volume of code that someone else must untangle.

Core workflow

  1. Describe the intended change and inspect the proposed requirements and work plan.
  2. Run selected tasks against the project, observing the generated changes and verification output.
  3. Review the resulting pull request and preview, then validate the actual user workflow before accepting or releasing the change.

What customers pay for

Subscriptions allocate credits and differentiate collaboration or capacity. Editorial hypothesis: compare cost per accepted feature with total human review and correction time included. A meaningful trial would use representative work with explicit acceptance criteria, a known codebase and a fixed spending ceiling. Record the number of attempts, incomplete changes and issues found after review. That makes it possible to distinguish cheap generation from cheaper delivery. For a builder, margin depends on model usage, sandbox time and support, while customer retention depends on whether accepted output remains useful after the initial demonstration.

Distribution signals

Observed channels and entry points; their performance is not inferred.

  • Agency outreach and live demonstrations

    Jain describes early direct outreach to development agencies, then content and referrals. These are founder-attributed channels without independently measured acquisition effects.

    Evidence

Trade-offs

  • Editorial risk: a broader automated workflow can increase value, but each additional integration introduces failure states and support obligations that a small team must maintain.
  • Editorial risk: credit allowances help contain compute expense, while opaque consumption can make buyers reluctant to iterate. Clear usage reporting and recovery from failed runs are important purchasing considerations.

Open questions

  • Which repeatable client-development task produces an accepted result with the least human correction?
  • How much review time and compute does one accepted feature require across ordinary and difficult projects?

A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.

Revenue evidence

Founder disclosure in interview
≈ $500,000ARR · Unspecified $ · 500K ARR reported in the March 12, 2026 interview; exact financial cutoff unspecified
Reporting period
500K ARR reported in the March 12, 2026 interview; exact financial cutoff unspecified
Figure as of
Not provided
Reporting method
Founder disclosure in interview
Source checked
Oct 20, 2026
Source published
Mar 12, 2026

The founder explicitly attributes 500K ARR to the standalone pre.dev product. Agency revenue is excluded, and the editorial 42K monthly header is not treated as measured MRR. Historical unaudited run rate, not collected annual revenue or profit; currency code unspecified. No inference is made about revenue from later Labs or licensing offers.

Arjun Raj Jain first-person interview, March 12, 2026
This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.

Current free plan includes 20 credits. Plus is $10/month or $99 billed annually; Premium $49/month, Pro $199/month and Team $499/month, with separate annual prices. RL tasks are quoted separately. These current plans differ from the March interview.

The source page may change its prices, limits, or offer after the recorded check date.

What founders can learn

Editorial notes

Turn a repeatedly used internal scoping workflow into a paid product, then test expansion into adjacent execution tasks.

Before you build something similar

  • Vendor claims of autonomous production readiness and benchmark superiority were not independently validated.
  • Agency-funded development and cloud-program participation do not establish an entirely bootstrapped capital history; external equity funding remains unverified.
  • Current Labs, code licensing and pricing changes must not be back-projected into the March ARR disclosure.

These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.

Source material

6 sources
  1. Founder product income interview Public source · Checked Oct 20, 2026
  2. Official coding agent product Public source · Checked Oct 20, 2026
  3. Official current pricing Public source · Checked Oct 20, 2026
  4. Official company LinkedIn size range Public source · Checked Oct 20, 2026
  5. Founder article describing two engineers Public source · Checked Oct 20, 2026
  6. Official founders and cloud program Public source · Checked Oct 20, 2026