Send us
the brief.
An engineer reads every brief that arrives here — the person who would scope the work, not a sales team. You get a reply within one working day. If we think you are asking for the wrong thing, that is the first thing the reply says.
Four things to
tell us.
You do not need a specification document or a technical vocabulary. Be clear about four things and we do the translation into architecture. Everything except your name, your email, and the brief itself is optional.
Project brief
What to include in your brief
The constraint
The budget ceiling, the regulation, the integration you cannot replace, or the team you have to work with. The real constraint shapes the architecture more than the feature list does.
The deadline
A date, and what happens on it. A funding round, a season, a contract renewal, a regulator. If the date is arbitrary, say that too — it changes what we recommend.
What already exists
A repository, an architecture sketch, a vendor contract, or an honest description of the spreadsheet holding it together. We would rather read the mess than a cleaned-up summary.
What success looks like
A number, a date, or a behaviour that changes. If nobody in your organisation can state it yet, that is the first thing we work on together.
If you would rather read how we work before writing anything, the doctrine states it in eight clauses, and capabilities lists what we actually do.
The register,
in full.
Work is remote-first and most engagements never need a room. The address below is the registered office of Cognimit Technologies LLP and the one on our invoices and statutory filings. Every identifier here can be checked against a government registry without contacting us.
Project enquiries and introductions.
- Phone
Answered during working hours.
- Hours
- Monday to Friday, 10:00–18:00 IST
- Timezone
- IST (UTC+5:30)
- Registered office
- Block - A, 606, Prahladnagar Trade Centre, Times of India Press Road, Vejalpur, Ahmedabad 380051
Gujarat, India
- LLPIN
- ACS-5305
Ministry of Corporate Affairs, India
- GSTIN
- 24AAVFC8309B1ZH
Gujarat, India
Send it to
the right place.
Six enquiry types, six routes. Using the right one saves you a forwarding step and a day. If you are unsure, use the form — we will route it ourselves.
- 01
New engagement
A platform to build, a rebuild, a migration, or a defined feature programme. Use the form on this page — it is read by the engineer who would scope it.
hello@cognimit.com
- 02
Embedded engineering
Engineers working inside your team, your stack, and your repository. Tell us the gap and the duration you are covering.
Monthly · dedicated allocation
- 03
Technology leadership
Fractional CTO, architecture authority, delivery review, or pre-build diligence for a board. Retainer, fixed hours, decision records.
Retainer · fixed hours
- 04
Venture and partnership enquiries
Distribution, white-label, investment, or strategic conversations about Aurelia, Voyazio, or AxleOne. These go to the founder, not an inbox.
3 ventures in build
- 05
Careers and applications
Open roles and the hiring process live on the careers page. Applications go to careers@cognimit.com and are read by an engineer, not filtered by a keyword parser.
careers@cognimit.com
- 06
Press and verification
Statements, founder comment, and company facts. LLPIN, GSTIN, trade mark class, and recognitions are published in full so you can check them without asking us.
ACS-5305
For quick questions during working hours, WhatsApp +91 93270 57103. Briefs are better sent through the form so nothing gets lost in a thread.
Four steps,
then a number.
The whole sequence takes about a week and produces a document you own, whether or not you engage us. There is no stage where you are handed to a different team.
- 01
An engineer reads it
Same working day. Not a sales team and not a form router. The person who reads your brief is the person who would scope the work, and they read what you wrote rather than a summary of it.
Day 0
- 02
A direct reply
Within one working day. It names what we think the real problem is. If we think you are asking for the wrong thing, you hear that first, before anything else.
Within 1 working day
- 03
A 30-minute technical call
Booked inside the same week. Constraints, existing systems, and the failure modes that matter. No slides, no discovery workshop, no second call to introduce a different team.
Same week
- 04
A written recommendation
Three to five working days after the call. Scope, non-scope, engagement model, and the number. Written down so you can circulate it, argue with it, or take it to another firm.
3–5 working days
Not sure which model fits?
Describe the problem and we will name the shape we would recommend — project delivery, embedded engineering, or technology leadership. Ventures we own are listed separately, and the doctrine explains the reasoning behind every answer above.