DB011 · Gate A1
Advisory
Judgment, on call.
Architecture reviews, build-versus-buy, hiring plans, the technical half of a decision your board is already asking about. You get an answer and the reasoning behind it, not a workshop.
BOARDING
Departures
Technical advisory, software development, and our own products, from one operator who has already crossed the ground you are standing on.
| Service | Destination | Departs | Gate | Status |
|---|---|---|---|---|
| DB011 | ADVISORY | ON REQUEST | A1 | BOARDING |
| DB022 | DEVELOPMENT | SCHEDULED | B2 | ON TIME |
| DB033 | OUR OWN PRODUCTS | CONTINUOUS | C3 | IN THE AIR |
One principal on duty. No bench.
All three run from the same desk. Most journeys change service at least once, and that does not cost you a new ticket.
DB011 · Gate A1
Judgment, on call.
Architecture reviews, build-versus-buy, hiring plans, the technical half of a decision your board is already asking about. You get an answer and the reasoning behind it, not a workshop.
BOARDING
DB022 · Gate B2
Working software, shipped.
Design and engineering delivered as working software. Scoped small enough to be real, run by the person who talks to you about it. No handoff to a team you have not met.
ON TIME
DB033 · Gate C3
Our risk, first.
We build and operate our own software, which means we carry the consequences of our own advice. What that teaches is what you are actually hiring.
See what we runIN THE AIR
Six passages, in the order they usually come up. Nothing on this board is a route we have only read about.
| Leg | Where you are | What we already know | Status |
|---|---|---|---|
| 01 Nothing built yet | You have a business and a conviction. No system. | The first architecture is the one you live with longest. We have picked wrong and paid for it. | SERVED |
| 02 It runs, but nothing holds | The first version works. Every change breaks something else. | This is not a discipline problem. It is a structure problem, and it is fixable without stopping. | SERVED |
| 03 Team outgrew the design | Headcount is climbing faster than the architecture can absorb it. | We have been the bottleneck in this exact room, and we know which parts of it are org and which are code. | SERVED |
| 04 Nobody knows why it works | The people who wrote it are gone. The system is load-bearing. | Archaeology before surgery. We have done both, in that order, on systems nobody wanted to touch. | SERVED |
| 05 Scale arrived early | Load found you before the design was ready for it. | The fix is almost never the thing the dashboard is pointing at. We have chased the wrong graph for weeks. | SERVED |
| 06 Rebuild or not | The highest-stakes call you will make this year. | We have argued both sides in earnest and been right and wrong on each. You want someone who has lost this argument before. | SERVED |
Our own aircraft · Gate C3
Duffel Bag Tech builds and operates its own software, in production, under its own name. That is where the advice gets tested before it reaches you.
A board only shows what is scheduled. What belongs here is real but not yet cleared to post, so it waits on standby rather than being invented into a departure.
TR 01
Track record
The roles, companies, and launches behind the practice.
Awaiting schedule
TR 02
Track record
The roles, companies, and launches behind the practice.
Awaiting schedule
TR 03
Track record
The roles, companies, and launches behind the practice.
Awaiting schedule
TR 04
Track record
The roles, companies, and launches behind the practice.
Awaiting schedule
WK 01
Named client work
Engagements go up once the client has agreed to be named.
Cleared, not posted
WK 02
Named client work
Engagements go up once the client has agreed to be named.
Cleared, not posted
WK 03
Named client work
Engagements go up once the client has agreed to be named.
Cleared, not posted
One conversation, then an honest answer about whether this is a fit. If someone you trust sent you here, say who: it changes which gate we start at.
Ask at the desk hello@duffelbagtech.com