RelayPay
Voice and chat support, with account checks and a real handoff to a person.
CHUKWU DIKE / SOFTWARE ENGINEER
PORTFOLIO / 2026I build AI agents, automations, and full-stack software. If your team keeps doing the same thing by hand, I can help turn it into a system.
Six automations from the Koya build series.
What they do, how I built them, and what I tested.
Voice and chat support, with account checks and a real handoff to a person.
A sales brief becomes researched leads and outreach drafts. Nothing gets sent automatically.
One researched idea becomes four content formats, with claim checks and an editor’s review.
Discovery notes become an editable proposal, with checks and a second person’s approval.
Three data sources, one report. Code calculates the figures before Claude writes the analysis.
Invoices from PDFs, emails, and scans become checked records, without duplicates or invented fields.
Newest builds first. The numbers come from the test records linked in each project.
I figure out the workflow first.
Then I build the checks around what the agent can do.
What are people doing now, and where does it get stuck?
Get the data and sources the agent needs.
Give the model a clear job and the tools to do it.
Check the facts, permissions, and anything missing.
Get the result to the right person, with enough context to use it.
I keep the sources, enforce permissions in code, and make room for human review.
How I built RelayPay ↗I’m Chukwu Dike. You might know me as psychemist. I like getting into the details, understanding how something works, and finding a better way to build it.
I work on AI automation and full-stack software. The agent is one part of the job. I also build the interfaces, APIs, data models, and review flows around it.
I’ve worked on cryptography and embedded systems too. That’s part of why I care about what happens when something fails, not just when the demo goes well.