translate

Translate Your Expertise Into a Product

You've spent years mastering your field. You know exactly which parts of the job suck. This skill helps you go from "I know this problem exists" to "here's what the software needs to do" — in language AI tools can build from.

Core Principles

• You don't need to learn to think like a developer. You need to describe the pain clearly. AI handles the rest.
• After 20 years, your daily workflow is already efficient. The opportunity isn't in your routine — it's in the pain you've learned to live with.
• The best SaaS products don't automate everything. They eliminate the one step that makes professionals say "I hate this part."
• Your domain expertise is the product spec. The hard part isn't building — it's knowing what to build. You already know.
• If you can't explain why it's painful to a stranger in 30 seconds, the pain isn't sharp enough to build a business on.

---

Step 1: Find the Pain Worth Building For

Don't catalog your workflow. Go straight to the pain.

Answer these five questions. Write one sentence for each — don't overthink it.

1. What task do you put off or dread, even though you've done it hundreds of times?
2. What takes way too long relative to the value it produces?
3. What makes you think "there has to be a better way" at least once a month?
4. What do you see junior people in your field struggle with that a tool could fix?
5. What would you pay $100/month to never do again?

Tell AI:

I'm a [your profession] with [X] years of experience. Here are my top pain points:

1. [Pain — what you dread or avoid]
2. [Pain — what takes too long]
3. [Pain — "there has to be a better way"]
4. [Pain — what juniors struggle with]
5. [Pain — what you'd pay to eliminate]

For each one, evaluate:
- How often does this pain occur? (daily, weekly, monthly)
- How many other [professionals in my field] have this same pain?
- Do existing tools solve this? If so, what's wrong with them?
- Could software realistically fix this, or does it require human judgment?
- What's the current workaround? How much does it cost in hours per week,
  dollars per month, or errors per quarter?

Rank them by: frequency × pain intensity × market size × buildability.
Tell me which one is the strongest SaaS opportunity and why.