Thirty minutes with a senior engineer
Not a discovery call with a salesperson. You describe what is not working; we sketch an architecture and give you an honest cost range. You keep both, whether or not you hire us.
Sealdah, Kolkata
Sealdah, Kolkata
West Bengal 700014, India
Urgent support for managed clients: 24×7 on the escalation line
Before you call, useful to know
Discovery start
Usually within 2 weeks
First response
Under 1 working hour
Proposal turnaround
2 working days
Languages
English, Hindi, Bengali
Send us the shape of the problem on WhatsApp
A screenshot, a link, a drawing, or two sentences. We will come back with questions and an initial view, usually the same day.
Have a brief?
Send it. We will come back with the assumptions we would need to confirm.
Have a website?
Send the link. We will run a performance and technical read before we meet.
Have neither?
Tell us what takes too long. That is enough to start a useful conversation.
From first message to a proposal you can act on
The first conversation is deliberately not a sales meeting. A senior engineer asks what is not working today, what you have already tried, and what a good outcome would look like as a number — enquiries per month, days to close month-end, hours of manual entry, cost per tonne. If you do not yet have that number, working it out together is a large part of what the call is for, and it is genuinely useful whether or not you engage us.
Within two working days you receive a written summary: our understanding of the problem, the shape of a solution, the assumptions we would need to confirm, and an indicative cost range with the factors that would move it. That document is yours. Several people have taken it to their board, decided to solve the problem internally, and come back to us two years later for something else. That is a perfectly good outcome.
Where the work is substantial, the next step is a fixed-price discovery: workshops with the people who own the outcome, an audit of what exists, and — for operations and plant work — a day on site watching how the work is actually done, with a stopwatch. Discovery produces a costed plan ranking every process by the hours it consumes and the money that leaks through it. That is the document your CFO reads, and you own it regardless of what you decide next.
We will tell you on that first call if a package product or another firm would serve you better. We have lost work this way and kept clients for a decade because of it.
Typical timeline
- 1Day 0You call or message. We reply within a working hour.
- 2Day 1–330-minute call with a senior engineer. Architecture sketch and cost range.
- 3Day 3–5Written summary with assumptions and an indicative range.
- 4Week 2Discovery begins if you proceed — fixed price, output you own.
- 5Week 4–6Costed plan, module sequencing and a firm proposal.
Who you will speak to
The senior engineer who would own your architecture — not a salesperson, and not a project manager relaying between you and an unnamed team. They stay on the project through delivery and you have their number.
Practical questions
If yours is not here, ask it on the call. We would rather answer a hard question early than discover a mismatch in week six.
Thirty minutes with a senior engineer, not a salesperson. We ask what is not working today and what a good outcome would look like in a number. You leave with a rough architecture sketch and an honest cost range, and there is no obligation. If we think a package product or another firm would serve you better, we say so on that call rather than three meetings later.
Within one working hour on WhatsApp and phone during business hours, and by the next working morning on email. Our median first response across all channels is under two hours. If it is urgent, call — the number reaches a person rather than a queue.
Yes, as standard, and before you send anything sensitive. Send us your own NDA or ask for ours. This is routine for us — a substantial share of our work involves commercially sensitive production, pricing and customer data.
Yes, and for anything substantial we prefer to. The first visit is at no cost anywhere in and around Kolkata, Howrah, Durgapur and Asansol. For plant work, a day on site changes the scope more than any amount of specification writing.
Whatever you have — a rough brief, a link to your current site, a screenshot of the report that takes too long, or nothing at all. What is most useful is a sense of what a good outcome looks like as a number: enquiries per month, days to close month-end, hours of manual entry. If you do not have that yet, working it out is part of what the call is for.
Yes, with a realistic start date. Discovery can usually begin within two weeks; build capacity depends on the size of the engagement and we tell you honestly rather than promising a date we will miss. If we cannot serve you in a reasonable timeframe we say so on the first call.
What makes a first conversation useful
You do not need a specification, a budget or a clear idea of the solution to call us. Most people who ring have a problem rather than a project, and working out what the project should be is the part we are actually good at. But a few pieces of context make the first conversation dramatically more productive, and they are all things you already know.
The most useful thing you can describe is the symptom rather than the solution. "Our despatch reconciliation takes two people three days every month" tells us far more than "we need an ERP", because the first is a fact about your business and the second is a guess about the answer. We have talked plenty of clients out of an ERP and into a two-week automation that fixed the actual complaint.
The second is who else has to agree. Projects stall far more often on approval than on engineering, and knowing early whether the decision sits with you, with a board, or with a parent company in another city changes how we scope and sequence the work. There is no wrong answer, but a surprise in month three is expensive.
The third is the deadline and what is driving it. An audit, a funding round, a season, a contract renewal or a system whose support ends are all real constraints we can design around. A date with nothing behind it usually costs money for no reason, and we will say so.
Call or WhatsApp +91 70033 91355 during working hours and you will reach an engineer rather than a call centre. If it is out of hours, WhatsApp is read first thing. Nothing you describe goes further than the people who would work on it, and we will sign an NDA before you share anything sensitive if you would prefer.
One more thing worth saying plainly, because people ask: there is no cost and no obligation attached to the first conversation, and we do not run a follow-up sequence afterwards. If we speak and it goes nowhere, you will not hear from us again unless you get in touch. We would rather have twenty honest conversations that produce three good projects than chase all twenty, and the referral rate that keeps this studio busy depends on people finding the first call useful whether or not they hire us.
Useful things to have to hand
- The symptom, in your words — what takes too long, costs too much, or gets lost.
- Roughly how many people are affected and how often.
- Who else needs to approve, and how quickly they usually move.
- The deadline and what is actually driving it.
- What you have already tried, including what did not work.
Rated 4.7 out of 5 across 64 reviews
Verified on Google Business Profile
Enquiries now arrive with specifications already attached
Our previous website had a stock photograph and a paragraph about commitment to quality. It brought us nothing in four years. Sayak spent two days on our shop floor before drawing anything, and what they built lists our machine capacities, tolerance ranges and certifications in a way a purchasing officer can actually evaluate. The change was not in the number of enquiries so much as in their quality — people now call having already decided we can do the job, so the conversation starts at commercial terms.
They talked us out of half of what we asked for
We went in with a long list of features we were certain we needed. They built roughly half of it and explained clearly why the rest would be maintained forever and used by nobody. Six months on they were right about every item. The store is fast on phones, which matters because that is where almost all of our traffic comes from, and our team updates the catalogue ourselves without calling anyone.
Parallel running for a full month meant nobody had to trust it blind
Replacing a system a clinic depends on is frightening, and most vendors we spoke to proposed a weekend cutover. Sayak ran the new system alongside our registers for a full month and only switched once the numbers matched every day. Our front desk staff were part of the design rather than being trained at the end, which is why they actually use it. Report preparation that took a person most of a morning now takes minutes.