Jeff Rick @jeffrick

Entrepreneur who is focused on helping other startup succeed. I recently exited a healthcare analytics company that sold after 10 years with a home run exit. Boston, MA Joined April 2009

Tweets

166
Followers

184
Following

324
Likes

42

Jeff Rick @jeffrick

5 months ago

@afigtrades Yup

10 0 2 247 0

View Details

Jeff Rick @jeffrick

6 months ago

@aymanalabdul @maitrisvc we have full AI solutions and the team who knows how to build products

0 0 1 20 0

View Details

Jeff Rick @jeffrick

7 months ago

5/ Full breakdown: [newsletter link] For teams that move fast on decisions—this is the model.

0 0 0 10 0

View Details

Jeff Rick @jeffrick

7 months ago

1/ We've been talking about bespoke software and context graphs. Here's what we're actually doing. At @maitrisvc we've rolled out Agentic Development.

4 0 1 36 0

View Details

Jeff Rick @jeffrick

7 months ago

4/ Results: 3-5x throughput, same-day delivery when needed, code you actually own. This isn't theoretical. It's how we're working now.

0 0 0 12 0

View Details

Jeff Rick @jeffrick

7 months ago

3/ Speed without governance is chaos. So we built in automated quality gates, security scanning, human architectural oversight. AI generates. Humans decide.

0 0 0 12 0

View Details

Jeff Rick @jeffrick

7 months ago

2/ One senior engineer orchestrating multiple AI agents. Delivering the output of an entire team. No layers. No sprint delays. Direct collaboration with the person building the product.

0 0 2 19 0

View Details

Jeff Rick @jeffrick

8 months ago

@RepJamesClyburn So we shouldn’t require a RealID to fly??? You are in the wrong side of an 80/20 issue and completely misrepresenting the facts. You are part of the problem.

0 0 0 4 0

View Details

Jeff Rick @jeffrick

8 months ago

@abbydphillip If you don’t want proof of citizenship to vote you are part of the problem.

0 0 1 9 0

View Details

Jeff Rick @jeffrick

8 months ago

3/ Still early. But the gap between "we should have a tool for that" and "we have a tool for that" is collapsing fast. Anyone else seeing this?

0 0 0 11 0

View Details

1/ Something's shifting. Six months ago, building a custom internal tool meant real investment. Time, money, coordination. You had to really want it. Now I'm watching the same work happen in days. Sometimes hours.

2 0 0 12 0

View Details

Jeff Rick @jeffrick

8 months ago

2/ The tools have changed. Claude Code, Cursor, Copilot—not just faster. They're changing what's worth building. Problems that were never worth solving because the ROI didn't pencil out? The math is different now.

0 0 0 29 0

View Details

Jeff Rick @jeffrick

8 months ago

This is the playbook. Not "equivalent but cheaper"—actually better because it's yours. The point about configuration is key. Companies have been spending years configuring software to approximate what they actually need. Now they can just... build what they actually need. We've done this at @maitrisvc with several internal applications over the past year. Same experience—tighter fit, features we actually need, deep integration with our existing systems. Your pivot read is sharp too. The winners in the stack will be the ones who make themselves easy to build with, not build on.

0 0 0 41 0

View Details

Jeff Rick @jeffrick

8 months ago

3/ Still early. But the gap between "we should have a tool for that" and "we have a tool for that" is collapsing fast. Anyone else seeing this?

0 0 0 11 0

View Details

Jeff Rick @jeffrick

8 months ago

2 0 0 14 0

View Details

Jeff Rick @jeffrick

8 months ago

0 0 2 36 0

View Details

Jeff Rick @jeffrick

8 months ago

Knowing the customer today is table stakes. The real value is seeing around the corner for them. That's where first principles thinking earns its keep—you can't just automate the current workflow if the current workflow is the problem. Sometimes the best bespoke solution isn't a better version of what they do now. It's helping them see what they should be doing instead.

1 0 1 16 0

View Details

Jeff Rick @jeffrick

8 months ago

This is the unlock I keep coming back to. "Really knowing them" is the hard part—and the part that doesn't get commoditized. We've started building bespoke tools for clients where their workflow is genuinely different. Not replacing their systems, but filling gaps between them. The stuff that used to live in spreadsheets and tribal knowledge. The cost math finally works. But the value comes from understanding their problem deeply enough to scope it right. That's still a human skill. Domain expertise + cheap code = serving the long tail of needs that were never worth building for before.

1 0 2 130 0

View Details

Jeff Rick @jeffrick

8 months ago

Why do we still bend our processes to fit software instead of the other way around? For 40 years the answer was obvious: custom = expensive, slow, risky. Starting to think that equation has flipped. Anyone else?