For partners — selected engagements only.

We take on a small number of long-arc software builds for partners we believe in. Privacy-first, on-device-first when applicable, and always written so the team can keep shipping after we hand off.

How we engage

1. 30-minute scoping call. No deck, no slides. We talk about the problem, the constraint, and whether we’re the right partner. Roughly four of every five inbound briefs end here — that’s by design.
2. Two-week discovery sprint. Fixed fee. We embed with your team, sketch the architecture, ship a working spike on the riskiest piece, and write the technical brief for the rest. If after the sprint either side wants out, we walk.
3. Build sprints with weekly demos. Sprint-based, weekly demo days, monthly review on direction. We bias toward shipping a thin slice of real product over polished WIP. Engagements run six weeks at the floor and as long as the work is worth doing.

What we build

We work in a narrow band where on-device ML, privacy-conscious data handling, and fintech infrastructure meet.

• Privacy-first AI features. On-device classification, redaction, summarisation. Useful when your users’ data is the thing you most need to protect — receipts, health records, internal documents, draft communications. Pattern-of-record: OpenAI / Anthropic with store: false; on-device runtimes via Core ML, TensorFlow Lite, or compiled ONNX. Server is the exception, not the default.
• Android + iOS applications. Production-grade native or hybrid apps that don’t ship a roundtrip to your backend for every action. Comfortable across Kotlin / Swift / React Native / Flutter; we’ll recommend the stack that matches your team’s hiring market, not ours.
• Fintech infrastructure. Bank-statement ingestion, expense workflows, KYC pipelines, reconciliation, ledger-light internal tools. Quantitative-trading background helps when correctness matters and the data shape is gnarly.

We say no to: agencies-of-record, white-label software, generic WordPress builds, and any engagement that requires us to be the permanent owner of your codebase.

Past work

• TrackSpends (in-house product, 2024–): the privacy-first Android expense tracker on Google Play. Reads transactional Gmail receipts entirely on-device; the only cloud round-trip is the OpenAI categorisation call, made with store: false so prompts aren’t logged. Public privacy policy at /legal/trackspends/privacy; codebase remains in-house.
• Quantitative trading & financial-engineering tooling (personal + partnership work): algorithms for automated trading developed during Mayank’s MSc Financial Engineering at WorldQuant University, plus a handful of partner engagements in fintech infrastructure — covered under NDA, so we can’t name the partners here.

Pricing & timeline

Engagements start at a six-week minimum. The discovery sprint is a flat fee (set at scoping, typically two weeks of one engineer’s time); build sprints are billed weekly against a not-to-exceed cap agreed at sprint planning. Retainer relationships negotiate this further.

If your project is shorter than six weeks, we’re probably not the right shape — there are excellent freelancers and design-build agencies who specialise in that size.

Why selected engagements only

We turn down roughly four of every five briefs that reach us. The ones we take, we take seriously — long arcs, technical depth, written so you keep shipping after we hand off. That cadence is what keeps the work good; scaling the inbound funnel would degrade it.

Common questions

Who owns the IP? You do — fully, exclusively, from day one. We retain the right to write generic post-mortems and reference the engagement (anonymised) in marketing; everything else is yours.

What stack do you work in? Whichever your team can hire for. We default to TypeScript / Python / Kotlin / Swift; we’ll happily learn your stack if the constraint is real.

Can you work with our existing team? Yes. We prefer that — permanent ownership of your codebase is anti-goal for us. The handoff is built into how we work.

Do you take equity-only work? No, but we’re open to mixed fee + equity arrangements where the equity is meaningfully priced and the fee covers our floor.

What happens after handoff? A defined support window (typically four weeks) at no additional fee, then optional retainer for ongoing collaboration. If you’d rather have the codebase, the documentation, and the runbooks and never speak to us again, that’s the cleanest hand-off and we’ll respect it.