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
Back to feedPost
Hot take: most AI freelancers lose deals in the discovery call, not on price. They open with tools, demos and a stack diagram, and the client hears one thing: another person selling software. The client already has tools. What they do not have is someone willing to tell them the process they want automated should not exist at all. The freelancer who wins says no first, diagnoses the bottleneck, then builds only what removes it. Selling AI is easy. Saying no to bad automation is the actual skill clients pay for.
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
Related posts
Before you add AI to your product, find the screen where your users already copy and paste.
That's usually where the real AI feature lives. Not a chatbot in the corner, but a step people already do by hand: summarising a ticket, drafting a reply, tagging an upload, pulling fields out of a PDF.
Here's the order I follow when a founder asks me to add AI to an existing SaaS:
1. Pick one workflow, not "AI everywhere." Watch where users leave your app to paste something into ChatGPT and come back. That round trip is your feature.
2. Keep the model behind your own API. One service owns prompts, retries, logging and cost limits, so you can switch providers without touching the frontend.
3. Make it tenant-aware from day one. Each customer's data, prompts and usage stay scoped to their account, or the first enterprise security review will stop you.
4. Ship a draft, not a decision. Let the AI suggest and the user approve. You earn trust and get real feedback before you automate anything.
5. Measure accepted output, not tokens. If users rewrite most of what it produces, the prompt or the context is wrong, and that's your real roadmap.
Most AI features that flop didn't fail because of the model. They were bolted onto the wrong step.
What's the one task your users still copy into ChatGPT?
Watching where users paste into ChatGPT and come back is such a practical way to find the real feature. Most teams start with the chatbot instead.
Ai generated, for entertainment purposes
Most of the design work in Publizo is stuff you never see on screen.
Take credits. The obvious way to build an AI writer is to write the article first and publish it after. But if your WordPress password expired or a token was revoked, the publish fails and you've already paid for an article that went nowhere.
So Publizo checks the connection to your site before it writes a word. If it can't publish, it stops, tells you what's wrong, and doesn't charge a credit.
Same with images. AI-generated photos are easy to spot, and stock photos repeat fast on a niche blog. Publizo uses real photos and keeps track of them per site, so the same photo never shows up twice on one blog.
And every article is saved to your library before it goes out. If the site times out halfway through, you still have the full piece, the image and the SEO fields.
None of this shows up in a feature list. It's what had to be right before I'd let it publish to my own three sites every day.
