INTAKE
Write the first paragraph.
The first step with IK Labs is short and written: send context, constraints, and what you would consider a good outcome. The reply comes from the engineer who would do the work - usually within one business day.
MEMO
Send a short brief.
Five fields. The last one is the only one that matters.
Read by Ivan Kniaziev. Reply within one business day in most cases.
WHAT HAPPENS NEXT
Three lines, in order.
A read.
Ivan reads the message himself. There is no triage queue.
A written reply, usually within one business day.
Substantive: questions about constraints, observations about scope, and an honest sense of fit. Not a form-letter follow-up.
One short call, only if it helps.
If both sides see a fit, we move to a 30-minute call. If not, the exchange ends here, in writing - politely.
WHAT TO WRITE
Good fits and bad fits.
GOOD FIT
- Good fit 1:
Long-lived systems where the second year matters more than the launch.
- Good fit 2:
Marketplaces, payments, operational platforms, internal tools - the work where edge cases are the product.
- Good fit 3:
Engagements where you want the engineer to also own the tradeoffs.
BAD FIT
- Bad fit 1:
Cold recruiting outreach for our team.
- Bad fit 2:
Generic vendor lists, RFPs, and pitch processes.
- Bad fit 3:
“Let’s start now and figure out scope later.”
We read everything. Replies come back in writing.
RECORD
- Founder-led studio in Delaware
- Limited engagements
- Direct email to the engineer who reads it
IK Labs, LLC · Delaware, United States