Recently, I realized something about sales.
Most of the time, after a demo call, when we ask, “So, are you ready to purchase?” and the client says, “I’ll get back to you,” we assume they need more information.
So we send brochures, offer discounts, and do multiple follow-ups.
But sometimes, that’s not the real problem.
The problem is urgency.
For example, if you’re selling a billing solution to a small business, they might think, “I can still manage with my manual bill book. It’s not urgent.”
But if we can clearly show them that manual billing is costing them LKR 50,000 every month through leakages, missed tax returns, or other inefficiencies, the decision suddenly becomes different.
It’s the same with a doctor. If they say, “You can do the operation next year,” you might wait. But if they say, “If you don’t do it within two months, your life is at risk,” you won’t wait.
I think sales is not always about giving more information.
Sometimes, it’s about helping people understand the cost of not taking action.
It’s human psychology. The better we understand how people think, the better we can sell.
I’m looking for a creative video creator who can turn software products into videos people actually want to watch.
Need someone who can create high-quality product launch videos, feature walkthroughs, and promo videos for https://t.co/3ph4FGSVcK and https://t.co/1ThqCarQUZ.
If you’ve worked on SaaS or product marketing videos before, I’d love to see your work.
Send your portfolio with pricing detail to [email protected].
If you’re trying to get into AI, don’t just chase the hype.
Be genuinely curious.
Build small things. Experiment. Break stuff. Learn every day.
People who enjoy the process usually go much further than people who are only chasing the opportunity.
Curiosity is still one of the biggest unfair advantages.
Recently, one of my friend told me he was planning to switch career and become a software engineer.
I asked what made him decide that.
He said he had built a couple of websites with Lovable, including his portfolio, and realized software engineers earn better.
I told him, “It’s a good idea, but spend some time understanding what software engineering actually is before quitting your job.”
That’s probably the best advice I could give.
AI has made software look deceptively easy. People build a landing page or a simple CRUD app and start thinking they’re software engineers.
That’s like saying I was a game developer because I spent hours playing Snake as a kid.
Don’t get me wrong. I’m not trying to discourage anyone from switching into tech. AI has made learning and building more accessible than ever, and that’s a great thing.
But don’t confuse using AI tools with understanding software engineering.
I’ve been building products and working with software engineers for more than 5 years. Even today, when I look at system design, scalability, architecture, security, databases, debugging, and writing production-ready code, I still feel there’s so much to learn.
AI is an incredible accelerator.
But it can also make people overestimate how much they actually know.
@tonytonggg Really like this perspective.
One thing I’m still struggling with is turning messy problems into clear decisions, especially when there are too many priorities competing at the same time.
Any practical advice on how you create that clarity?
Founders :
How do you manage your daily tasks?
I’m writing a lot at the start of the day, but I’m struggling to finish even 50% of them.
What mental models or frameworks do you use to prioritize what actually gets done?
When we build a very flexible culture in a company, we need to hire people with strong internal drive.
Otherwise, over time, we end up having to build the culture around supervision instead of trust.
Last few days I’m working on a small hobby project.
Built an MVP that automatically captures an entire website (with branches) using OpenCrawl.
It creates a mind map of any publicly available pages of website with page screenshots.
Do you think this would be useful for competitor analysis or quickly taking references?
AI coding doesn’t remove the need to understand what you’re building.
It just makes learning it 10x cheaper than it used to be.
Ship fast. But read what you ship.
For my first 2 months of vibe coding, I shipped without reading a single line of the code I was generating.
Then I started reading it.
Almost everything about how I build changed.
My prompts got sharper almost immediately.
Instead of “add Stripe,” it became “handle the webhook separately and make it idempotent, the charge shouldn’t depend on the redirect.”
Same tool. Completely different output.