Now Live AI Infrastructure Audit — Free 30-min review for SaaS & AI teams
Book Discovery Call
Home / Contact
3 open slots this week

Pick a time. Talk to a real engineer.

No SDRs, no discovery calls, no “let me loop in someone from sales.” The person whose face is on the slot you pick is the engineer you’ll be on the call with — and the one who’d do the work.

4-hour response, business hours
No CRM · no follow-up emails
Mutual NDA on request
If we’re not a fit, we’ll say so
The first 30 minutes

Here’s literally what the call looks like.

Most consultancies hide the first call behind “we’ll see what fits.” We don’t. The agenda is fixed, the people are named, and you’ll know in the first 25 minutes whether we should keep talking.

00:00 5 min
Intro

Who’s on the call, quickly.

One senior engineer from our side — named in the booking confirmation, with their LinkedIn and last three projects linked. No “the team” hiding behind a logo. 90-second context from you on what triggered the call. We get out of the way fast.

  • Named engineer on the call, not “the team”
  • Their relevant projects shared before the call starts
  • Your 90-second context, not a 10-minute pitch
00:05 10 min
Your situation

You talk. We listen.

What’s the actual problem — not the symptom. Where you are now, where you’re trying to be, what’s blocking it. Specific systems, real numbers if you have them. We won’t interrupt to pitch. We’ll only ask clarifying questions.

  • Current architecture & pain points
  • Budget reality — ballpark, no precision needed
  • Timeline pressure & political constraints
  • What’s already been tried that didn’t work
00:15 10 min
Our honest take

What we’d actually do.

The engineer gives a direct read on the situation. What sounds tractable. What doesn’t. What’s likely cheaper or faster to fix than you think. Whether we’re the right fit at all — and if not, who is. This part is the entire reason most teams find these calls valuable, even when nothing books.

  • Engineering opinion: is this 2 weeks or 2 months?
  • Cost ballpark for the realistic scope
  • Honest “we’re not the right fit” if that’s true
  • Specific competitors we’d recommend if relevant
00:25 5 min
Next steps

One of three things happens.

You leave with a clear path forward — or with permission to walk away clean. We won’t follow up unless you say to. No sequence of “checking in” emails. No “did you have time to think about this?” pings two weeks later. If we’re a fit, you’ll know how to move forward. If not, you’ll know why.

  • (a) Scoped proposal in writing within 48h, or
  • (b) Free written infrastructure review — no obligation, or
  • (c) Honest “not us” + 2 referrals to teams who fit better
Pick The Path That Fits

Four ways to start the conversation.

Different situations need different first moves. Pick whichever matches where you actually are right now.

Or Just Send Us a Note

Three fields. Reply in 4 hours.

If you’ve made it this far, you don’t need a 12-field form. Tell us who you are and one sentence about what’s going on. We’ll take it from there.

Quick message

Drop us a note.

A senior engineer picks this up directly — not a shared inbox, not a chatbot, not a sequence in HubSpot.

A real engineer replies within 4 business hours

What happens next

The exact timeline, from the moment you hit send

1
Within 4 hrs
A senior engineer reads it

Not a shared inbox. Hassan or Maryam, depending on what you wrote.

2
Same day
You get a real reply

Either a direct answer to your question, or 2–3 honest follow-up questions, or a calendar link with 3 slot options.

3
Day 1–3
If we book a call

30-min Google Meet with the engineer who’d run the work. No sales handoff. Same person on every call.

4
After
You decide — we don’t chase

If you reply, we continue. If you go quiet, we don’t follow up. Genuinely. No CRM nurture sequences here.

What People Say About The First Call

It’s not the project quote.
It’s the 30 minutes before it.

Most testimonials are about the work. These are specifically about what booking the first call felt like — because that’s what you’re deciding about right now.

The engineer joined the call having already read our docs and skimmed our GitHub. First 5 minutes, he was already pointing at the specific service that was overprovisioned. I’ve never had a sales call where the person came prepared.
Jenna Park
Jenna Park
VP Eng · Series B SaaS
They told us flat out “we don’t think you need us yet,” sent us two competitor names, and said to call back in six months. We did. Now they run our SRE practice. That intake call earned years of trust in 30 minutes.
Marcus Rivera
Marcus Rivera
CTO · FinTech, Series A
I booked expecting the usual sales theater. Instead I got a senior engineer who pulled up our actual CloudWatch dashboard on screen-share five minutes in and walked me through what he was seeing. That’s when I knew this wasn’t a normal consultancy.
Kavi Mehta
Kavi Mehta
Founder · AI startup
Live Activity

This page is active right now.

Updated nightly from our actual inbox and calendar. The point isn’t to humble-brag — it’s to show that “we’ll get back to you” actually means something here.

Inbound activity · live log
PKT · updated nightly
2 hours ago reply sent
Hassan replied to a Cost Optimization inquiry from Berlin — 11 minutes after it landed.
Yesterday · 4:20pm call booked
Maryam booked a Reliability Engineering first-call with a Series B SaaS — now scoping.
2 days ago referral out
Sent 2 competitor referrals after an AI Infrastructure call we knew we weren’t the right fit for.
Last week slot capped
Quarter capacity adjusted — 3 engagement slots remaining for Q3.
Last week free PDF
Free Infrastructure Review checklist downloaded 47 times in the last 7 days — no email required.
Median response time
1h 47m
Across all inbound messages this quarter, business hours
Calls this month
24
Of those, 11 became engagements · 6 became referrals
Open slots Q3
3
We cap concurrent engagements to keep quality — this is real, not theatre
Before You Click Send

The five things founders ask before reaching out.

Specifically about the contact experience — not the engagements themselves. The service pages have FAQs about those.

Skip to the form
Do I need to know what I want before the call?
No. Most of our best engagements started with “we’re not sure what we need.” Part of the first call’s job is to help you name the problem. If you can articulate the symptom (the bill, the latency, the on-call burnout), we’ll help you map it to the right scope of work — or tell you the work isn’t ours.
Will I get sold to?
No. The engineer on the call is the engineer who’d do the work — they don’t have a commission, a quota, or a deck. If we’re not a fit, they’ll say so on the call and give you 1–2 competitor names who’d be a better match. We’d rather lose one bad-fit engagement than fight to win it and deliver poorly.
Can we sign an NDA first?
Yes — happy to. Reply to the calendar invite asking for one and we’ll send our standard mutual NDA before the call. Or send yours; we’ll sign reasonable terms within 24 hours. We treat everything discussed as confidential by default regardless of paper, but we know your legal team might want the paper anyway.
What if our budget is small? Are we wasting the call?
Probably not. Most of our calls don’t become paid engagements — that’s by design. If your budget is small, we’ll tell you what you can realistically do yourself, what to read, what tools to look at. The reason we run this kind of intake is that small-budget calls today become big-engagement calls 12 months later. Or referrals. Or just goodwill in the community. That math works for us.
After the call, will you keep emailing me?
No. Genuinely no. No HubSpot sequences, no “just checking in,” no “still relevant?” emails six months later. If you reply, we continue. If you go quiet, we assume you’ll come back when you need us. The only exception is our monthly infra brief — one email a month, only if you explicitly subscribe to it. That’s the entire follow-up apparatus. By design.
You’ve read the whole page.
Pick a path above — or just send us three lines.
See the paths