A founder recently handed me a massive software suite to redesign, but they wanted to put every s...A founder recently handed me a massive software suite to redesign, but they wanted to put every s...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A founder recently handed me a massive software suite to redesign, but they wanted to put every single feature on the homepage at once.
Information overload makes users leave instantly. I pointed out that a homepage is just a router.
Its only job is guiding the user to the specific solution they need. I saw this exact same pattern when building Guppy AI.
The client came with a massive idea for a fintech platform with zero clear user flows. We needed to map out a data dashboard, custom AI agents, and team collaboration tools.
If I had waited for a perfect brief, we would have been stuck in planning for months. Instead, I took complete ownership of the UX and built rapid prototypes.
We reviewed them live so the client could react to real interfaces instead of abstract descriptions. When you start proposing solutions, the entire dynamic shifts.
You stop being a freelancer executing tasks and become a true partner. We ultimately finalized 54 screens in 3 months.
How do you handle projects where the client has a huge product but zero structural logic?
A strong specialist skill is useless if the wrong system gets invoked. Long-running AI work breaks in boring, expensive ways.
That is not a prompting problem. It is a routing and authority problem.
How I can help you:
I build project routers for teams using multiple AI workflows, agents, or specialist assistants so that they work with each other as a team.
I design source-of-truth resolutions so your agents retrieve the current rules instead of improvising or relying on assumptions or stale chat data.
I create reusable skill registries and specialist handoff logic hardened by determined and dedicated flow states reducing the need for model reliance on its own internal and displaced memory context.
I separate project states with individualized canonical states bound by rules living under essential model instructions and routed properly so unrelated workflows do not contaminate one another, but exist with awareness of the role each project plays, enabling a persistently growing ecosystem to develop organically.
I add governance wrappers, escalation hooks, and recovery mirrors around existing AI stacks so that trust is designed at the root, and variance is eliminated with rule based source archiving and implementation.
Trust means closing your eyes at night and sleeping soundly because your agents got your back. And I can put it all together for you, precision results sourced and undisputed because I got tired of doing things the hard way.
Phillip, agree that routing is where it breaks. In our builds the worst bugs came from an agent pulling an old rule from chat history instead of the current source. Pinning one source of truth per project fixed more than any prompt change did.
Static designs can't always showcase their full potential. That's why your architecture projects need a website that helps them reach their full potential.