contact · bengaluru-based · remote-first

Talk to the engineering team.
No salespeople, no decks.

GetWidget is a Bengaluru-based, remote-first AI development studio. Most replies in < 24 working hours (Bengaluru BST — we cover US, EU, UAE, IN working hours across the team). Book an audit, send an inquiry, or just say hi.

Or send a detailed inquiry
PHONE · BENGALURU +91 80 5003 2994
REPLIES < 24 working hours · Bengaluru BST
how engagements are priced

Three tiers, same as everywhere else
on the site.

Same pricing as every service pillar. Audit first to scope, pilot to ship one workflow, continuous to embed for the next ones. Walk-away clause after the foundation phase — if the data doesn't move, no phase 2.

what we need from you

A workflow, scope access,
and 30 minutes.

The discovery call goes faster when you bring these three things. None of them are blockers — we've run audits with just a Slack message describing the workflow. But the more concrete the input, the sharper the audit deliverable.

A workflow we'll audit

One concrete workflow with a problem statement, current monthly cost (people-hours, ticket volume, doc throughput — whatever the metric is), and what success would look like. We'd rather audit one workflow deeply than ten shallowly.

Read-only access scope

Read-only data tap to start — usually a CSV export, a sample of tickets/invoices/calls, or a sandbox API key. No write access until the pilot phase, no production data until we've signed an NDA + DPA where applicable.

A 30-min discovery slot

We run the audit on our side — you don't have to prep slides. The discovery call is a conversation: what you do, what's broken, what you've tried, where the AI work has to land in your existing systems. You bring the context; we bring the operator detail.

office locations

Bengaluru engineering HQ
+ Dallas mailing address.

Honest framing: Bengaluru is where the company was founded in 2017 and where most of the team works on-site. Dallas is a registered US mailing address for clients who need a US point of contact — there's no team on the ground there. We're a remote-first studio.

PRIMARY · ENGINEERING TEAM

Bengaluru, India

Founded 2017 · most of the team works here

Getwidget Labs Pvt Ltd
HD-101(A) WeWork Salarpuria Symbiosis
Bengaluru, Karnataka 560077
India
Hours · Mon–Fri 10:00–19:00 IST Phone · +91 80 5003 2994
REGISTERED MAILING ADDRESS

Dallas, Texas (US)

Mail forwarding for US clients · no team on-site

Getwidget Labs Pvt Ltd
539 W. Commerce St #1814
Dallas, TX 75208
United States
Purpose · Registered US mailing only For client meetings · we use Zoom / Meet — engineering is remote-first
What you get from the $3K audit

Five deliverables, one walk-away clause.
$3K, 1–2 weeks, no contract lock-in.

The audit phase is deliberately separated from the pilot phase. You pay $3K, you get a 90-day workflow roadmap with model picks and cost projection, and you decide whether to commission a pilot. If the audit says 'don't build,' you keep the deliverable and walk away — that's the whole point of the kill-point.

Or email us first
$3K fixed · 1–2 weeks Walk-away clause baked in NDA + DPA before any data touches our infra
contact faq

Questions we get on every
first call.

What time zones does GetWidget cover?

Most of the engineering team is in Bengaluru, India (IST / UTC+5:30). We cover US, EU, UAE, and India working hours across the team — early hours from Bengaluru overlap with EU/UAE afternoons; late hours overlap with US east-coast mornings. Discovery calls are flexible. Expect first replies within 24 working hours (Bengaluru BST).

Do you sign an NDA before the discovery audit?

Yes. We'll counter-sign your NDA before the discovery call, or send ours if you don't have one. For regulated workflows (healthcare, finance, legal), we also sign a DPA before any data touches our infrastructure — and we recommend doing the $3K audit phase on anonymized samples even after the NDA is in place, until the pilot kicks off.

Who owns the IP we build together?

You do. The audit report, the eval suite, the prompts, the workflow code, the deployment scripts — all of it transfers to you. We retain the right to reuse the operator patterns ("how to ship a tier-1 deflection agent") but not your prompts, your data, or your code. Standard work-for-hire terms in the pilot + continuous engagement contracts.

What happens if the audit says "don't build"?

You keep the $3K audit deliverable — the 90-day workflow roadmap, the model-cost projection, the risk-tier ladder — and you walk away. That's the walk-away clause baked into every engagement. We'd rather lose a pilot we shouldn't have sold than ship something that won't move the metric. Honest discovery is the whole point of having a separate $3K audit phase before any pilot money changes hands.

How fast can we start a pilot after the audit?

Typical sequence is: discovery call this week → audit deliverable in 1–2 weeks → pilot kickoff within 1–2 weeks of audit sign-off. So 3–5 weeks from "first call" to "engineers writing pilot code." If you're under a real deadline (board demo, regulator timeline, contract milestone), tell us in the form — we can compress the audit phase or run it in parallel with NDA/DPA paperwork.

Do you support US compliance — HIPAA, SOC 2, GDPR?

Honestly: yes for HIPAA-aware patterns (we ship Claude on AWS Bedrock with a BAA and PrivateLink VPC, audit-logged), yes for GDPR-aware DPAs, and partial for SOC 2 — we follow SOC-2-ready practices (audit logs, least-privilege IAM, key rotation, encryption at rest and in transit) but we are not ourselves SOC 2 Type II certified as a vendor. If your procurement requires a SOC 2 Type II report from the agency itself, flag that on the call and we'll route accordingly. For most regulated workflows the BAA / DPA + your existing security posture covers the gap.

Will I talk to engineers or salespeople?

Engineers. The discovery call is run by someone who'd actually be on your pilot — typically a senior AI engineer plus a product/PM lead. We don't have a separate sales team. The trade-off: we ask harder technical questions earlier ("what's the schema of that ticket data?", "what's your p99 latency budget?") rather than smoother demo-deck questions.

What models do you typically pick?

Per workflow, not per vendor. Long-context reasoning (200K+ tokens, contract review, multi-doc synthesis) usually lands on Claude Sonnet 4.6. Realtime voice agents go to OpenAI Realtime API for sub-600ms first-token. Cost-sensitive batch workloads run on open-source (Llama, Mistral) via Together or Groq. Regulated workflows on Bedrock with BAA. We'll tell you honestly when not to use a model — see our sibling service pages for /services/claude-development/, /services/openai-development/, and /services/ai-tools-and-frameworks/ for the per-vendor positioning.

not ready for the audit form?

Send a detailed inquiry
instead.

If the 3-field audit form is too short — for example, you have a long RFP, a procurement form to forward, or a multi-workflow scope to describe — email us directly. Same routing, same engineer reads it, no template-form gating.

PREFERRED: EMAIL

Tell us: the workflow(s) you want audited, the rough monthly volume / cost / team size involved, any compliance constraints (HIPAA / SOC 2 / GDPR), and your timeline. We reply within 24 working hours.

OR: BOOK THE AUDIT FORM

Three required fields (name · email · workflow). Two optional (company · phone). After you submit, you'll get a calendar link to pick a 30-min slot — or email us directly afterward.