Today Iโm excited to re-introduce @FerndeskHQ!
The first help center that never goes out of date.
At my last company, we shipped new product incredibly quickly. But as a small team, we never had the bandwidth to keep our docs up to date. We wanted to spend less time in support and more time growing the business, but our docs were a bottleneck.
So I set out to build a docs platform that keeps up with you.
Today, Ferndesk saves 100+ SaaS teams 20-50 hours/mo on docs, and counting.
In year two, we're going to help 1,000.
PSA - For anyone struggling to find a good @conductor_build, drop everything and switch to @capydotai
It's hands-down the best ADE I've used, and it's not even close.
T3 is great (last used it 5 weeks ago so it may have changed a lot).
Side chats: there's no way to use different models in the same "thread".
For example, I used to do a lot of code review with Astra, what I would do for bulk of my building with Opus or another model. I could not figure out how to do that in T3 at the time.
Apart from that, thread management was a nightmare. Capy has captains + built-in issue tracking. It's brilliant!
I also did not want to manage my own VPS for dev, and I wanted an easy way to get preview links, as well as run local sync, all of which I've been able to do on capy.
Also, the UX is significantly better.
It's a hundred small things
@elie2222@_skris@conductor_build@capydotai I've tried all the apps:
- t3 code
- amp
- superset (now paradev)
- paseo
- orca
- zed
- cursor
- hoplite etc etc etc
This was the first one that "clicked" after conductor.
It's a workflow + UX problem, not a model problem.
@conductor_build@capydotai - works with multiple subscriptions out of the box
- their app is a joy to use
- built-in issue tracking, pr monitoring, remote desktop, tunnels etc
- built in thread orchestration
- dozens of automations
very happy customer!
We built @SenjaHQ to $850,000 ARR without ever meeting
From sliding into his DMs, to almost 4 years working together
But last week we FINALLY met in Bangkok
@euboid it was fantastic to meet you and hang out IRL
Let's do it again soon ๐
Anybody who's been a @Railway customer over the last year could see the writing on the wall.
Yes the env leaks + downtime today are bad - but how could you tolerate having an outage every other week for months?
You shouldn't be using them for anything remotely serious. ATP even considering moving my hobby projects off.
https://t.co/sKoI1n8ps8
I love @Railway.
Been a happy customer for 5 years.
But today a caching misconfiguration let users see and act as other users. Names, personal data, medical info leaked between customers.
This after weeks of almost daily incidents.
It's time to switch. Alternatives?
It sucks big time because everyone knows I've been a HUGE Railway fan for years.
But I wouldn't be able to sleep at night with any of my services there, more so if they put bread on the table.
HugOps to them but with their track record + lack of communication during this incident - it's safe to say that I'll almost certainly never use them again.
I had to urgently switch our hosting from @Railway to @Render
In the past, doing so would've been a huge pain....
Migrating env vars,ย reconfiguring services, setting up internal networking, fixing broken builds etc.
Instead, I installed the Railway, Render, and @infisical MCPs and asked Codex to migrate us.
In a few hours it had unified our env management, configured all our Render instances, fixed broken builds.
All we had to do was update our DNS.
Exciting times!
It only took ~5 years but I finally met my cofounder @helloitsolly!
Almost 5 years ago I started my first company, Senja.
After building it in public for a while, Olly slipped into my DMs and asked if I wanted to build together.
I thought, sure, why not?
3.5 years later and we grew the business to 2K+ customers and $850K ARR before I left to start @ferndeskhq
He's just as ridiculous IRL ๐คฃ
Also ft. @nico_jeannen
In a world where you can build anything if you're ambitious enough, what should you build?
I've been thinking about this a lot, and I think I've landed on two filters:
1. How often does a team actually work in it? Daily beats weekly beats "one-off setup"
2. How close is it to revenue? Getting and closing customers beats running the back office.
*Ignoring market size, ICP, and infra.
Score high on both and growth and retention are easy. Score low on both and it gets a lot harder.
The launch was a success!
We ultimately got bodied by a Chinese 10+ person team ๐คฃ but still super happy with the results!!
- #2 product of the day
- 1K+ visitors
- dozens of new trials
THANK YOU SO MUCH FOR THE SUPPORT!!!
I want whatever the @ferndeskhq is drinking because they are on fire.
10 ships and 650 points gained ๐ฅ
Drop them some more suggestions to rack up those points even more!
https://t.co/xoRsSjogFJ