You read engineers async, on your time. They write their log. You decide who to introduce, who to interview, who to bring in. No pipeline calls. No screen-fatigue from LinkedIn.
LinkedIn is sync · you screen, you DM, you scan resumes. Proof is async · the candidate writes once, you read on your clock, you reach out only when you actually want to talk.
Four things this week. Five minutes each. By Sunday you will have read three engineers, taken one team read, and dropped one appreciation. That is the floor.
Your team isn’t lazy.
You’ve trained them to behave like a resource.
The fix isn’t a new comp band or a Friday all-hands. It’s rebuilding the room so a different behaviour is cheaper than silence. That is what ZMT Aware does.
A wall of substrate that did not exist for you before.
Engineers on Proof write decisions, stucks, learnings, and thanks. The wall is theirs. You read it. The ones whose stream matches the work you need to ship · you ask for an intro. RK reads the request, makes sure the timing is right for both sides, and connects you. No cold DMs. No resume screening.
Read your first curated log.
Open /f2/curated. Read one log. Notice how you read it differently than a LinkedIn post.
Curated logs are the ones RK marked as worth your time. Each one shows you how an engineer thinks · what they decided, what they got stuck on, what they took in. The substrate that does not fit on a resume. You will know within three logs whether a particular engineer's mind matches your team.
Take the culture assessment for your team.
Five minutes. The score tells you where your team sits on the Silent → Heard ladder.
Before you hire your next engineer, know what room they are walking into. The culture assessment scores how often the hard things get said out loud, in your room, to your face. Zero is not alignment · it is the silence. You will not change the score by reading it; you will change which engineer fits.
Drop one appreciation.
Name one engineer (or anyone) who shaped your work. Tell them something they have not heard you say.
Appreciation on Proof is not endorsement. Two fields · the thanks, and the line you NEVER said before. The shadow text is required · that is what makes it substrate, not LinkedIn noise. They approve before it goes public.
Request your first intro.
Pick one engineer from the pool whose stream matches the work you need to ship. Ask RK for an intro.
Intro requests are rate-limited (one per 30 days per engineer · so you do not spam, and the engineer does not feel hunted). RK reads the request, confirms timing on both sides, makes the call. Most intros land within three days.
What's different in your tier.
If your company is a ZMT Aware customer, three things change. Your org has its own dashboard with founder-specific surfaces. Your team's culture read is tracked year-on-year. Intro requests are unlimited, and you get monthly culture letters from RK reading the substrate you don't have time to read yourself.
You will have read three engineers, taken one team read, and dropped one appreciation..
That is the floor. The next week you read more, request one intro, and decide whether the engineer you read is worth a 30-minute call. The platform does not push you · you come back when you have a real opening to fill.
- You do not have to write anything · engineers write, you read
- Engineers do not see who has been reading their stream
- No algorithm ranks engineers · you read the wall yourself
- No guilt-trip emails if you skip a week
See you in the curated archive.
RK
Proof · Founder Onboarding · Issue 01
Radhakrishnan Selvaraj
Candor and Innovation
₹50L–₹100Cr a year is the cost of a team that is not safe to be stupid.
ZMT Aware · a year of structured culture work · founder signs publicly.
Real curated logs · the substrate the founder side reads.