INTAKE
Write the first paragraph.
Send context, the constraint that matters most, and what a good outcome looks like. I read it myself and reply within a business day - with questions, not a booking link.
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 steps, in order.
I read it.
Ivan reads the message himself. There is no triage queue.
You get a written reply.
Scope observations, fit honestly assessed - not a template follow-up.
One call, if it makes sense.
If both sides see a fit, we move to a 30-minute call. If not, the exchange ends here - politely, in writing.
WHAT TO WRITE
Good fits and bad fits.
GOOD FIT
- Good fit 1:
Systems where year two matters more than launch week.
- Good fit 2:
Marketplaces, payments, ops platforms - edge cases are the product.
- Good fit 3:
AI features that have to work in production - agents, filters, moderation, RAG, drafting with human review - not a prototype for investors.
- Good fit 4:
You want the engineer who builds it to own the trade-offs.
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