Question 1

Singapore is 13 hours ahead of New York. Doesn't that make collaboration impossible?

Accepted Answer

It makes casual collaboration impossible, which is why we don't rely on it. The engagement runs on a written handover in both directions plus one protected live window daily — 08:00–10:00 Eastern, which is 21:00–23:00 in Singapore, staffed deliberately rather than heroically. West Coast teams get the better end of it: your 17:00 Pacific is our 09:00, so end-of-day handoffs land at the start of our day. What you get in exchange is a genuine second shift — work queued at your end of day is in staging when you wake up. What it demands is written specifications, because a question that could have been a two-minute call otherwise costs a cycle.

Question 2

Who owns the code, the models and the prompts?

Accepted Answer

You do, assigned outright on payment — code, infrastructure-as-code, models, prompts, fine-tuning artefacts, evaluation sets and pipelines. Not licensed, not jointly held, not retained as reusable vendor IP. Singapore contract law is a well-tested seat for cross-border technology agreements and Singapore enforces intellectual property rigorously, which is a materially different position from some lower-cost engineering markets. If your counsel wants the assignment language reviewed before scoping, we will send it.

Question 3

Are you SOC 2 certified?

Accepted Answer

We do not hold a SOC 2 report, and we would rather tell you that here than in your security review. What we do provide is the underlying control set — role-based access control, time-bound and logged production access, encrypted connections, documented change management through CI/CD, and zero-retention model configuration — and we complete vendor security questionnaires directly. Where a SOC 2 report is a hard procurement gate, we will say so early rather than consume six weeks of your evaluation cycle. For engagements where we work inside your cloud accounts and your controls, your own attestation boundary is generally what governs.

Question 4

How do you handle US state privacy laws and Canadian requirements?

Accepted Answer

We design to the strictest regime in your footprint rather than to a lowest common denominator. In practice that means CPRA-grade handling of opt-out signals, sensitive-data categories and automated-decision disclosure, applied across states, so adding a jurisdiction doesn't trigger a rebuild. Canada is treated as a separate question, not a US extension — Quebec's Law 25 in particular carries consent and cross-border transfer-assessment obligations that catch teams assuming PIPEDA is the whole picture. We establish your footprint at scoping and design retention, consent and deletion to it.

Question 5

What is the tax and invoicing position for a US or Canadian company?

Accepted Answer

Straightforward, though not quite frictionless — we would be wary of any vendor claiming zero paperwork. We invoice in USD via wire, ACH or card. As a foreign entity performing services outside the United States we provide a completed W-8BEN-E for your vendor file, and payments to us are not reportable on Form 1099. We have no US permanent establishment, so there is no state nexus created by engaging us. Your controller will have processed foreign-vendor arrangements before; this is the ordinary version of one.

Question 6

How is an engagement scoped and priced?

Accepted Answer

Scoped against your systems, your compliance footprint and your delivery timeline before any number is discussed — we publish no rate card, because an agent platform with an evaluation harness and a marketing-site rebuild are not comparable units of work. Request a proposal and you will get a scoped architecture, a delivery cadence mapped to your time zone, and a milestone-based commercial structure.

Queue it at 5pm. Review it at 8am.

One working day, two time zones

What decides an offshore engagement, in our experience

A 13-hour offset is an asset or a disaster, depending on the handover

Your IP, assigned outright, under a jurisdiction that enforces it

Built for a privacy map that is now fifty conversations, not one

Where teams put the extra shift

Production agents, not wrapper scripts

Product and platform engineering

Technical SEO and programmatic search

Architecture for high-scale sectors

Fintech & insurtech

Real estate & proptech

Ecommerce & D2C

Logistics & supply chain

Infrastructure, controls and commercial terms

Deployed to your cloud, in your regions

Controls that survive a security questionnaire

Modern stack, 99.9% uptime target

USD invoicing, straightforward paperwork

The objections, answered directly

Add a second shift to your roadmap