Skip to content

Contact

Let’s build something impactful.

Tell me what you are building and where it is stuck. No form to fill in — email reaches me directly and I read all of it.

Ways to work together

Four shapes an engagement can take.

Find the line that describes your situation. The engagement follows from that, not the other way around.

  • You have a direction and no consensus

    A problem, scoped

    A short piece of work that ends in a written view of the problem and a recommended first build. Useful when the team disagrees about what to build next.

  • You need someone to own the product, not advise on it

    Product ownership

    Ongoing product work: roadmap, prioritisation, research, release planning, and the decisions in between. Freelance or contract, remote.

  • There is nothing to look at yet

    Build the first version

    Design and ship the initial product or a specific surface inside it. Design, frontend, AI integration and the automation behind it.

  • You are hiring, not contracting

    A full-time role

    Product roles with remote-first teams. The résumé page has the full history and prints cleanly.

What to contact me about

And what I will turn down.

Worth an email

  • A product that is stuck between an idea and a first version
  • An AI feature that demos well and fails in real use
  • A build that shipped and is not activating anyone
  • A product role with a remote-first team

Not a fit

  • Agency subcontracting and white-label delivery
  • Unpaid work framed as exposure or equity-only trials
  • Link exchanges, guest-post placements and SEO outreach

Writing the first email

Three lines are enough.

  1. 01

    What you are building

    One sentence. Stage, product, who it is for.

  2. 02

    Where it is stuck

    The thing that is not working — even if you cannot name it precisely yet.

  3. 03

    What good would look like

    The outcome you actually want in the next quarter.

Questions

Before you write

  • What kind of work do you take on?

    Product strategy and management, AI and automation builds, and growth execution — usually with founders and small teams who need one person to own a problem end to end. Freelance and contract, remote, working US hours where needed.

  • How does it usually start?

    A short call about the problem. After that I send back a written view of what I think the real problem is and what I would build first. If that is useful, we scope from there.

  • What is your response time?

    I read every email and usually reply within a day. Anything urgent, say so in the subject line.

  • Are you open to roles as well as projects?

    Yes — product roles with remote-first teams. The résumé page has the full history and is printable.

Two ways to reach me

Project & client enquiries

devchoprawork@gmail.com

Anything else

me@devchopra.life