47 actors, 539 users, and one actor with 62 percent of the runs

The drawing

The problem

In April 2026 we had no actors and no store presence. Building one actor at a time doesn't scale past a handful, and listings drift the moment two people edit them.

What we built

47 actors covering identity resolution, firmographics, hiring signals, tech stack detection, funding and press, social presence across nine platforms, contact classification, and page extraction.

The social family comes out of a generator plus one spec file each. Every build passes a QA gate. A daily health check watches the fleet, and a nightly reconcile mirrors store usage into our own database.

What it produced

Latest snapshot per actor, read September 9, 2026:

• 539 users, 65,671 runs, and 125 active users in the last 30 days.
• One actor holds 336 users and 40,629 runs. That's 62 percent of all runs in one product.
• 34 actors have fewer than 5 users. 9 have 5 to 19. 3 have 20 or more.
• 2 reviews across the whole fleet.

We publish the distribution because it's the useful part. It tells us which one is the product.

One defect is worth naming. 15 social actors declared per event pricing and never called the charge function, so they billed nothing. The charge now fires at the point each row is emitted.

The store's user count isn't cumulative and can fall, so 539 is a point in time figure.

Try it

Every actor prints its price per result. Start with the Mamba Labs GTM Suite on the Apify Store. If your use case needs something the fleet doesn't cover yet, reach out and tell us what the row should carry.