Tell me where you are, what is getting in the way and what progress would look like. We can work out the right shape of collaboration.
Ujjwal is the person you work with. Heerax Labs is the implementation arm, with responsibilities agreed for each engagement.
03Work with me
Four ways to contribute.
Sometimes the need is another person on the team. Sometimes it is a few weeks spent on one stubborn workflow. Here are the ways I can contribute, with the scope made explicit.
01 / Full-time product roles
Join your product team.
For a team hiring an Associate Product Manager, Product Analyst, AI Product contributor or Founder’s Office operator with a product focus.
Discovery needs structure, requirements need clarity, or a product team needs hands-on analysis and delivery support.
Deliverables
Problem and discovery briefs
Requirements, workflows and priorities
Product analysis and metric definitions
Cross-functional delivery support
Responsibility boundary
Contribution within an agreed role and reporting structure. No claim of executive product leadership or ownership of specialist engineering, legal or financial decisions.
How it starts
Share the role and team → discuss responsibilities and relevant work → follow your hiring process.
02 / Part-time product execution
Keep execution moving.
For founders and product teams who have a direction but need a defined contribution alongside their existing team.
The user, scope or first release is unclear; too many features compete; assumptions need a practical validation plan.
Deliverables
Problem, user and assumption map
MVP scope and alternatives
Prioritised workflows and requirements
Validation questions and next-step brief
Responsibility boundary
Research access and evidence collection are agreed explicitly. Recommendations are hypotheses where evidence is incomplete; implementation and commercial outcomes are not included by default.
How it starts
Review the context and available evidence → agree discovery scope → deliver and discuss a decision-ready brief.
04 / Heerax Labs implementation
Build something useful.
The service-delivery arm for a defined website, MVP or operational workflow that can be reviewed against agreed acceptance criteria.
A clear scope is ready to become a website, dashboard, internal tool or bounded AI-assisted workflow.
Deliverables
Websites and scoped MVPs
Dashboards and internal tools
AI-assisted or automation workflows
Reviewable build and agreed handover
Responsibility boundary
Integrations, hosting, data handling, production hardening, specialist reviews and maintenance are scoped separately. No enterprise-scale capability or ongoing support commitment is implied.
How it starts
Agree the workflow and acceptance criteria → build a reviewable slice → test the scope → document the handover.
Start with the context.
For a role, share the team and responsibilities. For a project, share the user, current workflow, timeline and intended result. Scope and deliverables are agreed before work begins.