Lemon Squeezy ↗
Developer toolsDigital product checkout with merchant-of-record services.
> $1,000,000ARR · USDhistorical milestone nine months after 2021 public launch
Researched profile Company/founder self-disclosure
NinjaPear
B2B research data for enrichment and prospecting workflows.
Reported revenue> $15,000Monthly revenue · Unspecified $Gross revenue for 'last month' in the July 7, 2026 interview; the financial month and cutoff are not explicitly datedOriginal disclosure
Business modelCredit-based API access through subscriptions and pay-as-you-go purchasesDeveloper tools
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff
Business overview
Public positioningA B2B company intelligence and enrichment platform supplying company, customer, competitor and person data through APIs and workflow interfaces. In the July 7, 2026 interview, Steven Goh explicitly calls himself NinjaPear's solo, full-time founder. That dates the evidence; current staffing and contractor involvement were not independently established. Prior exits and retained distribution assets provide material founder context.
How it makes money
Customers buy data credits through subscriptions or pay-as-you-go packs; endpoint and result depth determine consumption. The income disclosure is gross monthly revenue across the NinjaPear business, not subscription-only MRR.
Business breakdown
Researched Oct 20, 2026Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.
The customer problem
Official product evidence: NinjaPear exposes company intelligence and enrichment endpoints that can supply structured inputs to other software. Editorial interpretation: the customer needs usable research inside a workflow, rather than another disconnected list of facts. A suitable evaluation begins with one decision, such as deciding which companies merit further investigation, and identifies the minimum fields required for that decision. The customer can then judge whether an external data service reduces investigation work without introducing excessive correction, waiting or integration effort.
Core workflow
- Define a small representative company list and the fields needed for one concrete business decision, recording known reference answers where available.
- Request the corresponding enrichment through the documented interface, then inspect returned fields, missing answers and credit consumption.
- Pass accepted results into a test workflow and measure correction work, completion time and whether the output changes the intended decision.
What customers pay for
Editorial evaluation: use cost per usable record and time to a decision rather than raw API call count. Separate missing records from incorrect records because they create different downstream work. Measure latency across typical and difficult queries, and include retries, result review and integration maintenance in the total cost. Test whether an agent or application can handle absent fields without inventing an answer. Repeat a small reference sample when the supplier changes an endpoint or the underlying data. These are proposed acceptance checks; no live API queries, purchases or accuracy benchmarks were performed.
Distribution signals
Observed channels and entry points; their performance is not inferred.
- Retained newsletter and domain audience
The founder identifies existing audience assets as acquisition routes. This provides context for early distribution; it does not show that a new operator can reproduce the same acquisition cost.
Evidence
Trade-offs
- Editorial risk: deeper live research may offer useful context while increasing waiting time and making the result harder to fit into an interactive application.
- Editorial risk: credits support variable usage, while expiry and the stated subscription commitment can make irregular workloads more expensive than the headline credit rate suggests.
Open questions
- Which required fields can be checked against reliable reference information before the data enters an automated decision?
- Does the expected volume justify a subscription commitment after unused credits, latency and manual review are included?
Research sourcesFounder gross income and staffing interview Official current NinjaPear product on nubela.co Official current credit pricing and commitment terms Official January 30, 2026 data API launch and founder identity
A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.
Revenue evidence
Founder disclosure in interview> $15,000Monthly revenue · Unspecified $ · Gross revenue for 'last month' in the July 7, 2026 interview; the financial month and cutoff are not explicitly dated
- Reporting period
- Gross revenue for 'last month' in the July 7, 2026 interview; the financial month and cutoff are not explicitly dated
- Figure as of
- Not provided
- Reporting method
- Founder disclosure in interview
- Source checked
- Oct 20, 2026
- Source published
- Jul 7, 2026
Historical unaudited disclosure of over 15,000 in gross revenue for last month. 15,000 is a strict lower boundary, not an exact amount. Do not classify this mixed subscription-and-PAYG income as MRR or ARR, annualize it, or infer June 30 as the cutoff from publication date. Bare dollar currency is unspecified. The founder's separate $1M ARR goal is not achieved income; his earlier Proxycurl business income is excluded.
Steven Goh first-person interview, July 7, 2026This 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.
Pricing
Pricing pageOfficial pricing offers a 3-day, 10-credit trial, subscriptions and PAYG packs including a $10 starter pack. Credits expire; the subscription FAQ specifies a 12-month commitment. Bare dollar currency unspecified.
The source page may change its prices, limits, or offer after the recorded check date.
What founders can learn
Editorial notesPackage domain-specific research as paid data endpoints, then evaluate whether customers integrate the results into a recurring workflow.
Before you build something similar
- Gross monthly revenue is unaudited and combines payment modes without a recurring-revenue breakdown.
- The interview's last-month period has no explicit financial date; publication time is stored separately.
- Vendor statements about data provenance, accuracy and compliance have not been independently audited.
- This founder had prior exits and an existing audience; a two-week prototype does not establish equivalent starting conditions for a new operator.
These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.
Source material
4 sources- Founder gross income and staffing interview Public source · Checked Oct 20, 2026
- Official current NinjaPear product on nubela.co Public source · Checked Oct 20, 2026
- Official current credit pricing and commitment terms Public source · Checked Oct 20, 2026
- Official January 30, 2026 data API launch and founder identity Public source · Checked Oct 20, 2026