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 discovery 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 discovery 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 discovery 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 /ai-tools-and-frameworks/ for the per-vendor positioning.