3600LABS / FAQHONEST ANSWERS · 28 QUESTIONS · UPDATED MAY 2026
◆ FAQ · WHAT TEAMS ASK US FIRST

Honest answers,
not marketing.

The questions teams actually ask on first calls. If yours isn't here, send us a note - we'll add it (and email you the answer within a business day).

▸ GETTING STARTED · 6▸ HOW WE WORK · 7▸ FDE PROGRAM · 4▸ PRICING · 5▸ TECHNICAL · 4▸ AFTER LAUNCH · 2
SECTION 01

Getting
started.

The first questions almost every team asks on a discovery call.

06
01

What is 3600Labs?

3600Labs is an AI-native product studio. We design, build, and ship AI agents, SaaS platforms, dashboards, mobile apps, workflow automations, and internal tools. We work as a compact, senior engineering team - not as an agency. The first person you meet on a call is the engineer who'll architect your build.
02

How do we start?

+
Book a 30-minute discovery call from the Contact page. You walk a solutions engineer through the problem. We come back in 48 hours with a recommended shape (sprint, MVP, retainer, or FDE), a starting budget range, and an estimated timeline. If we're a fit, we send a fixed-scope SOW. If we're not, we'll tell you and recommend someone better.
03

Who do you work with?

+
Founders launching MVPs, SMEs modernizing operations, agencies extending their capability, and enterprise teams running AI pilots. We've worked with companies from seed-stage startups to large enterprises. We bias toward teams where decisions move fast and engineering is taken seriously.
04

Do you sign NDAs?

+
Yes. We sign a standard mutual NDA before discovery details are shared. Most of our work is under NDA - which is why our public case studies are anonymized. We'll send named references on request after first contact.
05

Where are you based? Do you travel?

+
Bengaluru, India. We work remote-first but our Forward Deployed Engineers travel - we've shipped on-site engagements across India, the UAE, and the UK in the last 18 months. International FDE deployments are quoted including travel and accommodation.
06

How does the first call work?

+
30 minutes. You walk us through the problem - users, current setup, the outcome you want. No SDR, no qualification quiz. The solutions engineer asks hard questions, takes notes, and tells you on the call whether we can help. If we can, you'll get a written recommendation and budget within 48 hours.
SECTION 02

How we
actually
work.

The mechanics of an engagement - who you talk to, how we ship, what's different.

07
07

How are you different from a traditional dev agency?

+
Agencies wait for 40-page requirements docs and then execute tickets. We work as a product and engineering partner. The first person you meet is the one who'll architect the solution. We push back when something shouldn't get built. We simplify scope. We ship working software in week one, not month two. And we tell you when AI isn't the right answer.
08

What's a "Solutions Engineer"?

+
A senior engineer (5+ years) who also does customer discovery, scoping, and architecture. They're not a sales rep with a tech vocabulary - they write code. On a discovery call, they'll ask you about your stack, your constraints, your data, and your team. By the end of the call, they'll have a working hypothesis for the system. They stay on the project as technical lead.
09

Do I get a project manager?

+
No. You get direct Slack access to the engineer building your thing. We've found that PMs add latency and lose context. For larger engagements (3+ engineers), one engineer takes the "tech lead" role and runs the weekly demo + planning, but they're still writing code daily.
10

Can you work with our existing team?

+
Yes - this is half our work. We plug in as an external product squad, an AI implementation partner, an automation team, or an engineering extension. We're comfortable shipping into someone else's codebase, following their conventions, and handing back PRs your team reviews. We do code review for your engineers too if useful.
11

Do you only build AI products?

+
No. Plenty of what we ship has zero AI in it. We use AI where it actually solves a problem cheaper, faster, or better. For everything else, we use boring, reliable software. We'd rather tell you "you don't need AI for this" than sell you a hallucinating chatbot.
12

How big is your team?

+
Intentionally small. We're under 15 people. Every project gets 1–4 senior engineers, a designer when needed, and a solutions engineer as technical lead. We don't grow headcount to chase pipeline - we accept fewer projects and ship them well.
13

How fast can you start?

+
Discovery in days. Scope locked in week one. First working build by end of week two. We have 1–3 slots open at any given time - sometimes we can start next week, sometimes there's a 4–6 week queue. We tell you on the discovery call.
SECTION 03

The FDE
program.

Forward Deployed Engineering - when, why, and how it works.

04
14

What's a "Forward Deployed Engineer"?

+
An FDE is a senior engineer who deploys to your office for 1–4 weeks and ships software next to your operators. They sit at a desk in your warehouse, factory, retail store, or hospital. They watch how invoices actually get processed. They notice the spreadsheet macros nobody documents. They build the right tool, in context, with your team. It's the model Palantir and the best AI labs use - and it's how we ship internal tools that actually get used.
15

When does an FDE pay off vs remote work?

+
FDE pays off when the problem lives on-site: warehouse ops, hospital workflows, retail floors, factory lines, field-force operations. Or when adoption has failed before - usually because the previous tool was built far from the people who use it. For pure software products with digital users, remote is fine. We'll tell you which fits.
16

What does an FDE deployment cost?

+
FDE deployments are quoted individually based on length, location, and the build scope they support. Includes the engineer's time, travel, accommodation, and per-diem, plus the actual build work. Most combine with an MVP Build or Internal Tool Build package. International deployments are quoted separately.
17

Who pays for travel?

+
We do. Travel, accommodation, per-diem, and any equipment the engineer needs are bundled into the FDE quote. You don't get a surprise invoice for flights. Domestic deployments are typically straightforward - international involves slightly more setup (visa, longer lead time).
SECTION 04

Pricing &
contracts.

Money questions, scope changes, payment terms, and the legal bits.

05
18

Why fixed price, not hourly?

+
Hourly billing aligns nobody. We're incentivized to be slow, you're incentivized to micromanage, and scope creeps until everyone is unhappy. Fixed price aligns us on outcomes - we win when you launch fast and the system works.
19

What if scope changes mid-project?

+
It will, and that's fine. We track changes as written addendums to the SOW with their own scope and price. Small changes (under 10% of project value) are usually absorbed. Bigger changes get a written change order before any work happens. No surprise invoices.
20

What are your payment terms?

+
Typical: 40% on SOW signing, 40% at midpoint demo, 20% on production deploy. For smaller sprints, we do 50/50. Retainers are billed monthly in advance. We bill in USD and accept payment via bank transfer or international wire (USD/EUR/GBP).
21

Do you work with international clients?

+
Yes. Roughly a quarter of our work is international (UK, UAE, US, EU). We invoice in your currency at a quoted rate. Standard payment terms, standard MSA available, GSTIN provided for Indian compliance.
22

Will you sign our MSA / vendor paperwork?

+
Usually yes. We've signed MSAs and framework agreements for enterprise clients without issue. For unusual clauses (uncapped liability, work-for-hire on pre-existing IP, etc.), we negotiate. Our standard SOW is short, clear, and reviewed by counsel - happy to share it on a discovery call.
SECTION 05

Technical
& ownership.

Stack, IP, security, data - the engineering and legal foundation.

04
23

Who owns the code and IP?

+
You do. Full source, infrastructure access, documentation, and runbooks are yours from day one. The code lives in your Git org. The infrastructure lives in your cloud account. No lock-in, no proprietary platform you have to keep paying for. If we vanish tomorrow, your team can keep shipping.
24

What's your tech stack?

+
We pick based on the problem. Common defaults: Next.js + React for frontend, Node.js / Python / FastAPI for backend, Postgres for primary data, Redis for cache, Vercel / AWS / GCP for deploy. AI: OpenAI, Anthropic, Gemini, LangChain, LlamaIndex, pgvector. Mobile: React Native + Expo. But we'll use what your team already runs if there's a reason to.
25

How do you handle data security & compliance?

+
Code in your Git, infrastructure in your cloud, secrets in your secret manager. For LLM work, we default to enterprise tiers (no training on your data) and offer on-prem / VPC-deployed open-source models where required. We've shipped under SOC2, ISO 27001, HIPAA-adjacent, and DPDP-Act compliant requirements. Security questionnaires answered honestly and quickly.
26

Can you work in our existing codebase?

+
Yes. We'll spend day one reading the code, the conventions, and the CI. We'll match the style, not rewrite it. PRs go through your normal review process. If we recommend a refactor, it'll be a separate explicit scope. We've worked in monorepos, microservices, and the occasional legacy PHP codebase.
SECTION 06

After
launch.

Support, maintenance, hiring, and how we hand off cleanly.

02
27

Do you provide support after launch?

+
Yes. Every project includes a 30-day on-call window after production deploy - bugs we shipped are bugs we fix, free, no questions. Beyond that, you can move to a Build Partner retainer (continuous capacity), an architecture review retainer (quarterly), or pay-per-incident on-call. Or step away - you own the code.
28

Can you help us hire our own engineers?

+
Yes. We've helped clients hire their first 1–3 engineers - defining the role, writing the JD, running technical interviews, and onboarding the new hires onto the codebase we built. The goal of most of our engagements is making ourselves replaceable. We're happy to support that explicitly.
◆ STILL GOT A QUESTION?

Send a note.
We'll reply.

A solutions engineer reads every inbound and replies within a business day - even if it's not a fit, we'll point you somewhere useful.