Studio practice
A product portfolio should show its working
By Siddhant Sharma · Published
Give the claim a source
A portfolio is easier to evaluate when its claims have somewhere to lead. Public app listings establish that a product exists. Actor listings expose descriptions, inputs, pricing and usage information. A registration number identifies the business behind the work.
These sources answer different questions. An MSME registration does not prove that a tool works. A product listing does not establish how much a business earns. Keeping those distinctions clear makes the evidence more useful.
Keep the date attached
Public figures change. The studio’s Apify profile statistics have a capture date, while the Actor catalogue reads a separate public API. When the API cannot be reached, the website uses a labelled, dated snapshot.
A total for each Actor should not be summed and described as unique people across the studio. The same person can use several tools. The portfolio keeps profile totals and Actor-specific counts separate.
Make status explicit
A published product, a project idea and a proposed partnership each represent a different level of commitment. Workflow ideas on this site are described as proposed scopes, while released products link to their official listings.
The same principle applies to recognition and support. A program’s existence is not an approval, and a partnership invitation is not an endorsement.