Your app can pass every planned test and still fail real users. That’s where exploratory QA comes...Your app can pass every planned test and still fail real users. That’s where exploratory QA comes...
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
Hey frens, for years I could do much of the work around a new product:
Define the opportunity.
Clarify the audience.
Shape the positioning.
Map the customer journey.
Write the MVP brief.
Plan the launch.
But turning that thinking into a working product usually required another dependency: a developer, technical co-founder, agency budget, or a long wait.
That has changed.
AI-native building tools have become a practical technical execution partner in my work—effectively, an always-available CTO for the early stage of an idea.
Alongside my work as a Hands-On CMO, entrepreneur, and investor, I have added two new hats:
Web developer.
Software builder.
Not because AI replaces experienced engineers, product designers, security, or serious technical architecture.
But because it lets a commercially minded operator move from a clear business problem to a real, testable first version much faster.
A recent example is Viewly by Realto: a focused PropTech workflow designed to turn property interest into a structured viewing request.
The problem is familiar. Someone sees a property, asks for a viewing, and the process becomes a chain of calls, messages, email follow-ups, availability checks, delays, and sometimes a lost lead.
Viewly gives the prospect a clearer path: explore the property, choose a suitable time, submit details, and move toward a confirmed viewing—while the business receives a structured enquiry rather than another unorganised message.
The lesson is bigger than real estate.
The first entrepreneurial bottleneck is no longer always technical execution.
It is clarity:
• Who is the first user?
• What recurring problem do they have?
• What is the smallest useful outcome?
• What can we test before building too much?
The winners will not be the people who generate the most AI apps.
They will be the people who turn real friction into focused, usable products.
I wrote more about the shift from writing briefs to building the first version here:
Testing my app! 🧰🚀 Everything is finally coming along.
I’ve been working on this project for a little over two weeks. Initially it was just me working with one AI agent, but I was still manually coding most of it, so I was moving like a turtle 🐢very slow.
Then I decided to implement Codex into my project to automate more of the development and it has been amazing. Now I can focus more on prompting, testing, reviewing the code and making the technical decisions instead of manually coding everything.
I also created my own AGENTS.md bible with all my project rules and instructions to make sure Codex follows them as the final authority when working on my code.
The idea is simple: create one useful and intuitive ecosystem of tools that Shopify merchants can add to their stores to help customers make purchasing decisions faster and with more confidence.
Still testing, building and adding more tools. Let’s see where this goes! 🚀
And if anyone finds the idea interesting. I’m definitely open to collaborations, ideas or partnerships. Feel free to reach out!