About

A small senior team, and a named engineer accountable for the work

Webilogic is an engineering studio, not an agency with a bench. The work below is what we do, how we run projects, and when we are reachable — stated plainly, because the alternative is asking you to take it on trust.

Founder and lead engineer

Sanket Gajera

9 years building software, 5 of them on IVR and telephony in production. That work has run from contact center builds and IVR modernisation through to the systems behind them — APIs, data models, integrations with whatever the client already had, and the operational tooling nobody budgets for until the first incident.

The most demanding version of it has been healthcare: telephony EVV for Medicaid home care, where a caregiver clocks in from a member's phone and the visit has to reach a state aggregator in that state's format, on time, or the agency does not get paid. Systems where the failure path matters more than the happy path teach habits that carry into every other project.

Outside telephony, most of the work is web applications, Node.js backends, and — for last stretch — AI automation wired into systems that already exist. The through-line is the same: build something a client's own team can operate after we leave.

How we work

  1. 01

    The person who scopes it builds it

    There is no handoff from a salesperson to a delivery team you have not met. Whoever writes the estimate is in the code, which keeps the estimate honest.

  2. 02

    Your repository, your cloud account

    Code is committed to your repository from the first day and infrastructure runs in your AWS or Azure account. Nothing has to be migrated at the end, and nothing is held hostage by a renewal.

  3. 03

    Scope is written down, including the exclusions

    Every proposal states what is not included alongside what is. It makes the number defensible internally and it prevents the argument in week nine.

  4. 04

    Weekly working software, not status reports

    Demos run against a staging environment you can click through yourself. A percentage-complete figure is not evidence of anything.

  5. 05

    We say no to work we should not take

    If a project needs a specialism we do not have, or more hands than we have, that comes up during scoping rather than after signing. A referral is a better outcome than a bad delivery.

Where we are, and when we are reachable

We are based in India and work with clients in the US, UK, and Europe. Contracts are direct, in your currency and under your law. Client data stays in your cloud account and your region — we build there rather than copying anything to a workstation.

In practice the distance costs one thing: we do not take 8am ET stand-ups. Everything else — design reviews, demos, cutover calls, incident bridges — happens inside the overlap window or on escalation.

Overlap
9:00am–1:00pm ET, every weekday
Monitored
Messages to 6:00pm ET
Escalation
24/7 for production incidents
Reply
Within one business day

Start with a call

Forty-five minutes with an engineer in the room. Bring the system, not a summary of it.

Start a project