Claude Design, HeyGen HyperFrames etc. all converged on HTML. It's funny because HTML is usually dismissed as basic/primitive. You would expect the future of design to look like something entirely new. But models were trained on billions of webpages, so their HTML fluency beats everything else.
Currently working on a side project for fun, and I decided to turn off AI-assist. It feels good to write code on your own again sometimes, deal with debugging, and occasionally visit StackOverflow 😅
If I were running a service business (roofer, lawyer, pest, whatever), here is exactly how I’d run my intake.
First things first. Twine is your number one asset.
Not your website. Not your Instagram. Not your “please leave a voicemail.”
Twine.
Most revenue leaks happen before anyone “does sales.”
Calls go missed. Texts get forgotten. Form fills rot. Webchat is a graveyard. Staff turnover resets everything. You do not have a lead problem. You have an attention problem.
If a new client is worth 3k to 5k lifetime and you miss even 2 decent leads a week, you’re lighting a used Tesla on fire every month.
People love spending on ads/SEO bc it feels like progress. Meanwhile the phone rings into the void. Iconic.
Here is what I would do from day one.
1. make one inbox for everything
Twine becomes the unified inbox for calls, texts, form fills, webchat, referrals.
One timeline per customer.
Every message, every attempt, every note, every outcome.
No more “who talked to them” or “did we ever call them back” or “wait i think that was the other number.”
2. speed to lead becomes a system. Set Twine to respond instantly, every time:
missed call: immediate text + callback offer
form fill: immediate confirmation + next steps
after-hours: clear expectations + urgent routing
during-hours: hold the place in line and route to the right person
Your front desk should not be a single point of failure.
3. qualify before a human touches it
Twine should collect the 6 to 10 things your team always asks anyway:
service needed
location
urgency
property or case type
photos or details
preferred timing
Then routes correctly.
You want humans doing high-leverage work: quoting, scheduling, closing.
Not asking the same intake questions 40 times a day.
4. follow-up is where the money hides
Most leads don’t say yes immediately. They just… drift.
Twine runs the follow-up loop automatically:
“still want to get this scheduled?”
“we have availability tomorrow afternoon”
“quick question before we send the estimate”
Until they book, decline, or go cold with a label.
If you’re not doing structured follow-up, you’re paying for leads you refuse to harvest.
5. hoping customers will leave reviews on their own
Give every employee a review badge and make it a rule:
Every completed job ends with a review ask.
Twine’s review badge pulls up the review link instantly.
Tap the customer’s phone to the badge. Review page opens. Done.
No texting links later.
No “we’ll send it to you.”
No friction. No forgetting.
6. track what’s actually happening
You need a single view of:
total inbound by channel
missed calls and save rate
response time by rep
booked rate by source
reasons leads didn’t book
Most teams argue about “lead quality” bc they can’t see the pipeline. Twine makes it boringly obvious.
7. the sneaky part: consistency across locations and phones
Multiple offices, crews, practice areas, or phone numbers means multiple ways to lose customers.
Twine standardizes the experience while still routing by:
office
service type
language
urgency
on-call rotation
Customers experience one organized company instead of six inboxes in a trench coat.
one more thing
answer your phone
but if you can’t, don’t pretend you did.
Twine’s whole job is: nobody falls through cracks, ever.
Because the person searching “dentist near me” rn is not loyal. They are friction-intolerant. If you don’t respond, they tap the next result. Simple as that.
local SEO, ads, whatever: those are amplifiers.
Twine is the plumbing.
Get the plumbing right first, then pour gas on the fire.
I want to thank the @CongressionalAC and the U.S. House of Representatives for providing me with a platform to submit my app, NexusAI (https://t.co/byFBLv22Ce), and receive this beautiful medal in recognition for winning the competition.
Unfortunately, I could not attend #HouseOfCode due to interference with school. However, I received an amazing letter from Rep. Nehls encouraging me to continue with the development of my app. NexusAI currently has ~100 active users and has received great feedback from its users!
also @supabase, i'm a 17 year old running a YouTube channel teaching others how to code.
I recently launched a video teaching how to build a C.R.U.D. app using your platform and would like some feedback :)
here's the link: https://t.co/WiuTIAAkVe