Contact
How to reach Raza Rizwan, what to bring to a first conversation, and what happens in a workflow audit.
- Status
- stable
- Trust
- human-reviewedhuman:rrizwan98 ·
- Owner
- human:rrizwan98
- Approved
- human:rrizwan98 ·
| rrizwan1998@gmail.com | |
| +92 303 2206662 | |
| GitHub | github.com/rrizwan98 |
| linkedin.com/in/raza-rizwan98 | |
| Based in | Karachi, Pakistan; works with teams anywhere |
What to bring
One workflow where a person still babysits the AI, or still does the whole job by hand. The more ordinary and repetitive it is, the better it works as a first project. Useful to say in the first message:
- what the job is, and what a finished result looks like
- who does it today, and how often
- which tools it passes through
- where a person must keep the final say
What happens first
A workflow audit. The current process is mapped step by step, the human steps are counted, the highest-value automation point is identified, and success is defined. It ends with a recommendation: whether a focused pilot is worth building, and what it would cover. If the answer is that automation is not worth it for that workflow, the audit says so.
What comes after, if it is worth it
Pilot, then production, then optimization, each earning the next. The four moves are described on how I work.
What is not discussed in public
The internals of systems built for clients or for a company: architecture, prompts, agent names, client names, the technology inside a delivered system. Those belong in a conversation under the client's own terms, not on a website.