2bros1ai_
forward deployed engineers

Forward Deployed Engineers: Affan & Furkan Dindar

Scroll. We'll explain everything.
the title

Wait. What's a Forward Deployed Engineer?

Hottest job title in tech right now, and it sounds way more mysterious than it is. Someone on the internet explained it better than we ever could, in two minutes, with Stewie. Watch that first.

Reel by @peterstewiestartup. We didn't make it. We just do it. Watch on Instagram ↗ Original creator: @peterstewiestartup
who-does-what.sh

$ cat who-does-what.txt

> A software engineer builds the product.

> A consultant explains the product.

> An FDE shows up and makes it work for YOUR exact problem.

$ ▍

  • Sits inside your company for weeks. Sometimes months.
  • Learns how the business really runs. It's never in the docs.
  • Wires up the systems, writes the code, ships the dashboards.
  • Production code, running in the real world. Zero slide decks.
That's the job. That's us.Except there are two of us and we share a last name.

Your systems don't talk.
We make them talk.

keep scrolling
the mess

Buying software is the easy part.

Then reality shows up. This is what a typical customer's sales stack looks like on a Monday.

Everything talks to everything. Nothing agrees. And a spreadsheet is secretly running sales.

Running Zoho, HubSpot or Pipedrive?

See what we wire into each

Meet the two guys who show up.

Affan

Affan

Full-Stack Dev
Furkan

Furkan

Full-Stack Dev

We're brothers. Not the kind that argue about the TV remote. The kind that argue about whether your CRM needs a migration or a wrapper. (Wrapper. It's always the wrapper.)

We taught ourselves to code in a basement, on one crappy laptop, before we could legally drive. Fifty-something shipped projects later, companies started calling us when the integration nobody wanted to touch had to get done.

We don't need Slack to communicate. One starts the function, the other writes the return statement.
four jobs, one team

An FDE is four hats.We take turns.

fix(integration)
ship(feature)
> tests pass

Software Engineer

We write the code that connects your systems. In your repo, your stack, your CI.

wrap > rewrite
events > cron
boring > clever

Solutions Architect

We decide what to wrap, what to replace and what to leave alone. Mostly leave alone.

now
next
later

Product Manager

We turn 'the ops team is annoyed' into a scoped, shippable backlog. With numbers.

1. here's what to do
2. (we do it)

Consultant

We'll tell you what to do. Then we do it. That's the whole difference.

how a deployment works

Parachute in. Wire it up. Leave it running.

Day 0

We land.

Laptop in hand, in your office or in your Slack. We sit with the sales and ops teams, read the docs, then ignore the docs and watch how a lead actually moves. Every system gets mapped. Yes, including the spreadsheet.

First weeks

We map the spaghetti.

Which systems talk, which pipelines lie, which custom fields nobody dares to delete. We decide what to wrap and what to replace (almost always wrap), and we agree on what 'working' means, with numbers attached.

The build

We wire it up.

Production code in your stack. Integrations, an agent plugged into your CRM, your database, your documents and your billing. Safely: scoped, logged, with approvals where they belong. Dashboards people actually open.

Handoff

We leave it running.

Documentation humans can read. Monitoring that pages the right person. Training for the team. Then we leave, or we stay embedded. Your call. Not a hostage situation.

Furkan and Affan together
Bonus

Fix it five times, it becomes a product.

When we see the same problem at five customers, the one-off fix turns into a real feature. You stop paying for the same fix. We stop writing it. Everyone wins except the spreadsheet.

The week-by-week version, with what we need from you: how we work →

Things We've Shipped

(That actually work in production)

These are our own products. We've sat on the vendor side of the table too, so we know exactly what happens when a customer's data doesn't match your schema.

Company & Process Management

Every approval a group of companies runs, on one platform

For a group of energy companies: leave, travel, expenses, purchases, company stamps and finance sign-offs, routed from a live org chart. Signed PDFs file themselves into SharePoint, sign-in is Microsoft 365. Live since June 2026.

120 people8,000+ signed PDFsMedian approval < 17h
ZOHO CRM · HUBSPOT · SALESFORCE · PIPEDRIVE · 400 CUSTOM FIELDS · LEADS_FINAL_V7.XLSX · LEGACY ERP · CUSTOM APIS ·  ZOHO CRM · HUBSPOT · SALESFORCE · PIPEDRIVE · 400 CUSTOM FIELDS · LEADS_FINAL_V7.XLSX · LEGACY ERP · CUSTOM APIS ·  ZOHO CRM · HUBSPOT · SALESFORCE · PIPEDRIVE · 400 CUSTOM FIELDS · LEADS_FINAL_V7.XLSX · LEGACY ERP · CUSTOM APIS ·  ZOHO CRM · HUBSPOT · SALESFORCE · PIPEDRIVE · 400 CUSTOM FIELDS · LEADS_FINAL_V7.XLSX · LEGACY ERP · CUSTOM APIS ·  ZOHO CRM · HUBSPOT · SALESFORCE · PIPEDRIVE · 400 CUSTOM FIELDS · LEADS_FINAL_V7.XLSX · LEGACY ERP · CUSTOM APIS ·  ZOHO CRM · HUBSPOT · SALESFORCE · PIPEDRIVE · 400 CUSTOM FIELDS · LEADS_FINAL_V7.XLSX · LEGACY ERP · CUSTOM APIS ·  
0+
Projects Shipped
0+
Years as a Team (Since Birth)
0
Slide Decks Delivered
0%
Brother-Powered
AI AGENTS · CRM · SUPPORT DESK · BILLING · DOCUMENTS · GUARDRAILS · PRODUCTION CODE ·  AI AGENTS · CRM · SUPPORT DESK · BILLING · DOCUMENTS · GUARDRAILS · PRODUCTION CODE ·  AI AGENTS · CRM · SUPPORT DESK · BILLING · DOCUMENTS · GUARDRAILS · PRODUCTION CODE ·  AI AGENTS · CRM · SUPPORT DESK · BILLING · DOCUMENTS · GUARDRAILS · PRODUCTION CODE ·  AI AGENTS · CRM · SUPPORT DESK · BILLING · DOCUMENTS · GUARDRAILS · PRODUCTION CODE ·  AI AGENTS · CRM · SUPPORT DESK · BILLING · DOCUMENTS · GUARDRAILS · PRODUCTION CODE ·  
REACT · NEXT.JS · TYPESCRIPT · PYTHON · SWIFT · KOTLIN · POSTGRES · AWS · DOCKER ·  REACT · NEXT.JS · TYPESCRIPT · PYTHON · SWIFT · KOTLIN · POSTGRES · AWS · DOCKER ·  REACT · NEXT.JS · TYPESCRIPT · PYTHON · SWIFT · KOTLIN · POSTGRES · AWS · DOCKER ·  REACT · NEXT.JS · TYPESCRIPT · PYTHON · SWIFT · KOTLIN · POSTGRES · AWS · DOCKER ·  REACT · NEXT.JS · TYPESCRIPT · PYTHON · SWIFT · KOTLIN · POSTGRES · AWS · DOCKER ·  REACT · NEXT.JS · TYPESCRIPT · PYTHON · SWIFT · KOTLIN · POSTGRES · AWS · DOCKER ·  

Okay. Where do we land?

Tell us about the CRM with 400 custom fields nobody owns, the spreadsheet that secretly runs sales, or the AI pilot that never left pilot. In 30 minutes we'll tell you whether we can wire it up, roughly how long it takes, and what it costs. No pitch decks. On either side.

Affan & Furkan as kids

Affan & Furkan Dindar

Deployable now

Not ready for a call? Ask the third bro.Built by us, trained on us. He doesn't get commission.