Skip to content
Contact

Tell us what you’re trying to build.

The more concrete the better: the actual problem, the constraint you're stuck on, or the thing you're not sure is possible. Half-formed ideas are welcome. Vague ones are harder to help with.

Transmission
New enquiry
01Subject

02Origin

03The problem

What are you trying to build, or what's the problem? Detail helps.

Or email hello@peakminds.co.in

We use what you send here to reply to you, and for nothing else. No analytics, no third parties beyond the email provider that delivers it. How we handle it.

How this works

What happens if you say yes.

Three shapes of engagement. Most work starts at the top and moves down, and we would rather tell you a review is enough than sell you a build you don't need.

011–2 weeks

Architecture review

You have a system, or a plan for one, and want to know where it breaks before you commit to building it. We read the code and the constraints, then write down what we found.

StartsA call, then read-only access to the repository and whatever design notes exist.

What you get

  • A written architecture assessment: boundaries, data flow, failure modes
  • A decision log with the tradeoff each choice accepts, stated explicitly
  • A prioritised list of what would break first, and what it would cost to fix
024–8 weeks

Prototype sprint

An open question that needs to become a running system before anyone can judge it. We build the part that carries the actual risk first, so the answer arrives early rather than at the end.

StartsA scoping conversation to agree what the risky part actually is. If we disagree with your framing, you hear that before you commit.

What you get

  • A running system that tests the hard part, not a demo that avoids it
  • An honest account of what worked, what did not, and what stayed uncertain
  • The evaluation setup used to decide, so the result can be re-checked
  • Handover: source, architecture notes, and how to run it
033 months+

Build engagement

Taking a system into production and keeping it there: typed contracts, real data models, background work, and the instrumentation to see what it does once it is live.

StartsUsually after a review or a prototype. Starting cold is possible but we will want a short discovery phase first.

What you get

  • The system, in production, with its deployment and rollback path
  • Observability: what it is doing, what it costs, and where it degrades
  • Documentation written for whoever maintains it after us
  • A defined handover, including the parts we would do differently

Ownership, IP and confidentiality

Ownership
You own the code and everything produced for you, on payment. We keep no licence over your product.
Reuse
Generic tooling and patterns not specific to your domain may be reused. Nothing that identifies you, your data or your business logic ever is.
Confidentiality
We will sign your NDA. If you would rather use ours, we have one.
Publishing
Nothing about your work appears on this site without your written agreement. The portfolio here is currently all self-initiated for exactly that reason.

Good fits

  • 01Systems where the hard part is architecture, not surface
  • 02AI features that need to be reliable, not just demoable
  • 03Infrastructure and tooling for AI-heavy codebases
  • 04Research questions with a buildable prototype at the end

Less good fits

Marketing sites, template-driven builds, and anything where the brief is mostly visual.

We’d point you somewhere better. Saying so early is cheaper for both of us than finding out three weeks in.