Dominic Holt

I spoke with the CTO of a $10B company last week. He told me legacy modernization is about to get commoditized - and most agencies are f*cked. His exact words: "Technical debt cleanup is going to India for pennies on the dollar." The reason: AI tools are making basic refactoring trivial. Developers in India with Cursor and Claude can rebuild entire legacy systems at a fraction of current costs. But here's what he's betting on instead: → Capacity building over code rebuilding → Strategic IT innovation over system migration → Turning engineering teams into business accelerators "Anyone can move from Bootstrap to React now," he said. "The real value is helping teams think strategically about what they build next." The companies winning in the next 3-5 years will have engineering teams that can: • Spot business opportunities through technology • Build competitive advantages, not just features • Turn technical capabilities into market positioning Most companies don't just need better code. They need better thinking.

337

212 Comments

So which models produce HTML that has the least accessibility errors, and at what cost? Mapped it out here (bottom left is the best). This is helpful for understanding which models are most compliant for those with disabilities and do it efficiently. Qwen and Gemini 2.5 Flash lead the pack. Hat tip to Ben Ogilvie for pointing me to this: aimac.ai

51

2 Comments

Today I am excited to announce Digger’s BIGGEST update ever Project OpenTaco - The Open Standard for Terraform automation. With OpenTofu, where Digger is a founding member, the community already has a credible open-source CLI alternative to BSL-licensed Terraform. But as we all kno that only solves half the problem. The CLI helps teams avoid lock-in, but it doesn’t address governance or collaboration challenges at scale. Project OpenTaco builds on this foundation, without taking an opinion on which IaC language is used, giving teams a path to adopt more Infrastructure-as-Code with a TACOs that is open, self-hostable, and free from licensing traps or per-resource pricing. We believe that it this is “Terraform’s backstage moment”. Backstage became the open standard for Internal Developer Portals, we believe Project OpenTaco will do the same for IaC automation, setting the standard, driving adoption, and making closed platforms unnecessary. The future of IaC is open, and we’re building it brick by brick. Check out our roadmap and sign up for updates, we’d love any and all feedback! Link in the first comment ->

98

11 Comments

All in! We've raised $4M in seed funding at Reo.Dev.🚀 Next stop: ... Making Developer Intent incredibly obvious for every DevTool GTM team out there! AI infrastructure is advancing so fast, and with it, developers are gaining more say in how software gets bought. Developer teams explore and evaluate very differently. They download package installs, interact with code commands, and make open-source contributions. These adoption signals indicate real usage. But the problem is they’re off-platform and remain invisible to traditional CRMs and intent platforms. This is exactly why we built Reo.Dev - It surfaces these real evaluation signals and enables developer-focused companies to understand, map this behavior across organizations, and prioritize their GTM efforts accordingly. Each one of you have made a dent in what Reo has become - and where it’s headed next, so glad to have you on this journey with us 🙌 : Nirmata, Unstructured, deepset, LangChain, Ververica | Original creators of Apache Flink®, DataHub, Appwrite, Chainguard, Akka, Bitrise, Cortex, Tigera, CrewAI, Union.ai, Synadia, n8n, Appsmith, Unleash, Galileo, Tetrate, Temporal Technologies, Upsun (formerly Platform.sh), Plotly, & more... Grateful to have partners who are invested in this mission with us: Heavybit, IndiaQuotient, Foster Ventures Its been so rewarding to see Reo.Dev enable users with AI-powered visibility that helps them make better GTM decisions and create more revenue opportunities!💪 Building like it's day 1!🚀

568

84 Comments

𝟭𝟬 𝗥𝘂𝗹𝗲𝘀 𝗳𝗼𝗿 𝗮 𝗖𝘂𝘀𝘁𝗼𝗺 𝗖𝗥𝗠 💸 I lost $86K not following these. Don’t do the same. 𝟭/ 𝗕𝘂𝗶𝗹𝗱 𝗳𝗼𝗿 𝗮𝗰𝘁𝗶𝗼𝗻, 𝗻𝗼𝘁 𝗮𝗿𝗰𝗵𝗶𝘃𝗲𝘀 Most CRMs become cluttered databases. Design it to move deals forward. → What do you need to do, not just track? → How fast can someone complete their next task? ✅ Example: → Don’t say: “Status: warm lead” → Say: “Follow up in 2 days — send proposal” 𝟮/ 𝗞𝗲𝗲𝗽 𝗶𝘁 𝘀𝘁𝘂𝗽𝗶𝗱 𝘀𝗶𝗺𝗽𝗹𝗲 You’ll always overbuild. Fight that urge. → 3 core tables: Contacts, Deals, Activity → Automate later, not first ✅ Example: → Don’t add 18 fields to log a call → Just track: Who, What, When, Outcome 𝟯/ 𝗟𝗶𝗻𝗸 𝗿𝗲𝗹𝗮𝘁𝗲𝗱 𝗱𝗮𝘁𝗮 Context is everything. → Every deal links to a contact → Every contact links to a company → Every activity links to both ✅ Example: → Click a deal → see emails, calls, invoices → No tab-hopping to figure out what’s going on 𝟰/ 𝗦𝗲𝘁 𝗿𝗲𝗺𝗶𝗻𝗱𝗲𝗿𝘀, 𝗼𝗿 𝗹𝗼𝘀𝗲 𝗱𝗲𝗮𝗹𝘀 No follow-up = no money. → Add "Next Step" to every deal → Auto-remind reps when nothing’s scheduled ✅ Example: → Don’t say: “In proposal stage” → Say: “Call on Thursday to confirm pricing” 𝟱/ 𝗨𝘀𝗲 𝘃𝗶𝗲𝘄𝘀, 𝗻𝗼𝘁 𝘀𝗲𝗮𝗿𝗰𝗵 Speed = trust in the system. → Create saved views: → “Deals Closing This Week” → “Leads With No Activity” → “Clients Past Due” ✅ Example: → Don’t make reps filter manually → Feed them exactly what they need each morning 𝟲/ 𝗔𝗹𝗶𝗴𝗻 𝗶𝘁 𝘄𝗶𝘁𝗵 𝘆𝗼𝘂𝗿 𝗲𝘅𝗮𝗰𝘁 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 Templates are generic. Your ops aren’t. → Map: Lead → Deal → Quote → Close → Build just for that flow — nothing else ✅ Example: → Don't use default HubSpot junk → Build Airtable views that match your pipeline 1:1 𝟳/ 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝘁𝗵𝗲 𝗯𝗼𝗿𝗶𝗻𝗴 𝘀𝘁𝘂𝗳𝗳 Your reps shouldn’t be typing “Sent proposal” in 2025. → Automate task creation → Log emails + calls with Make.com → Trigger follow-ups from checkboxes ✅ Example: → Mark deal as “Won” → send welcome email + invoice instantly 𝟴/ 𝗧𝗿𝗮𝗰𝗸 𝗽𝗮𝘆𝗺𝗲𝗻𝘁𝘀 𝗶𝗻𝘀𝗶𝗱𝗲 𝘁𝗵𝗲 𝗖𝗥𝗠 Sales isn’t closed until cash is in. → Add fields for: Deposit, Balance Due, Payment Method → Track outstanding amounts per deal ✅ Example: → Deal says “Closed” → But invoice shows: $500 still unpaid. That’s not closed. 𝟵/ 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 𝗳𝗼𝗿 𝗮𝗻𝘀𝘄𝗲𝗿𝘀 You don’t want “data.” You want decisions. → Total active deals → Total closed won this month → Sales rep leaderboard ✅ Example: → Use Airtable Interfaces → CEO sees pipeline at a glance — no calls, no spreadsheets 𝟭𝟬/ 𝗧𝗿𝗮𝗶𝗻 𝗹𝗶𝗸𝗲 𝗶𝘁’𝘀 𝗮 𝗿𝗲𝗮𝗹 𝗼𝗻𝗯𝗼𝗮𝗿𝗱𝗶𝗻𝗴 The CRM doesn’t fail. People just never use it. → Loom videos → SOPs in Notion → Weekly cleanup sessions ✅ Example: → Monday morning = CRM hygiene check → “If it’s not in the system, it doesn’t exist Let's Go

35

10 Comments

If you’re still on the Apollo GraphQL Legacy plan, this is for you. We’ve seen a huge influx of teams moving over to WunderGraph Cosmo recently. Almost all of them are making the move because of the changes Apollo is rolling out to their plans that are due EOY. A lot of people think using GraphQL or GraphQL Federation automatically means you need an enterprise contract. That is not the case. Many teams are stuck on Apollo Gateway or being pushed into new plans they do not want. With Cosmo, you do not have to go down that road. Our entry plan starts at $500 a month and includes up to 250M requests per month. For most teams, that is more than enough to run Federation at scale! I could tell you what the experience is like post migration, but it’s probably better to hear it directly from our customers: https://lnkd.in/dcejF9Dh If Apollo’s changes are forcing your hand, it is worth looking at your options. A picture is worth 250M requests per month 😉

29

1 Comment