Software Development · Austin, Texas

Trusted by teams at Explore the work

From Little Ideas To Space

Software development and engineering in Austin, Texas: custom apps, data, and AI for teams that move fast.

Start a project See our work

Consulting Services

Yee Code Editor

ET1 Analytics

Break, Build, Sleep, Repeat

Behind the game below

One story, 10 versions

We built this explainer 10 times: 7 versions with Claude Code and 3 with Codex. The one below is Claude #5. Every one of them is a click away.

Claude Code
Codex

Claude Code · 7 versions, built in this repo as Astro + three.js components

Claude #1Shelved

Built like a movement

An exploding mechanical watch movement: mainplate = diagram, jewels = interviews, mainspring = voice, gear train = backlog, escapement = agents, dial = systems. Shelved: the metaphor needed translating and the scene was cluttered.

Open full page (opens in a new tab)

Read this version’s story 9 steps

One movement, every part made in-house A fine watch is hundreds of parts that only work because they were made to mesh. Custom software is the same. Scroll to take ours apart.
Diagram the targets and milestones Everything in a movement mounts on the mainplate. Ours is the diagram: your systems mapped, targets exposed, milestones pinned, and requirements gathered before a line of code is written.
Interview the people, connect the dots Jewels are the bearings that take the friction out. Ours are interviews. We talk to the people who do the work, then link what they said: the spreadsheet finance re-keys is the export ops dreads.
Voice becomes text becomes signal Every interview is recorded and transcribed. NLP tags the systems, pain points, cadences and asks, so the energy in a conversation gets stored instead of lost in someone’s notes.
The backlog writes itself Tagged phrases become epics, stories and acceptance criteria, each traceable to the person and the minute it came from. Gears transfer energy. The backlog transfers intent.
Thousands of AI agents, one tempo The escapement releases power one tick at a time. dev3lop spawns and orchestrates thousands of AI agents against that backlog, claiming, building, testing and reviewing on a steady beat, with our engineers setting the tempo.
Your systems, streaming into one place Cloud-agnostic and on-prem capable. Your clouds, databases and APIs stream into one platform we build end to end, from web apps to Electron and C++ desktop software.
A drawer of good parts is not a watch One vendor for discovery, another for notes, another for the backlog, another for the build. Nothing meshes, context leaks at every handoff, and profit stalls with it.
Energy flows straight to the hands When one team owns the plate, the jewels, the spring, the gears and the escapement, nothing is lost between them. Time saved compounds, and so does margin.

Claude #2

Build Order (RTS)

A real-time-strategy base builder on a fixed isometric board: dev3lop is the HQ. The dev3lop cursor scouts your systems, interviews your people, turns speech into a build queue and sends 4,096 agents to build it; every cloud, database and API runs a supply line to HQ; then the map is replayed with four vendors and an illustrative J-curve shows profit growing. Judges ranked the pitch #1.

Open full page (opens in a new tab)

Read this version’s story 9 steps

One company runs every step This is a short strategy game about how we build software. dev3lop is the headquarters in the middle of the map, and every step you are about to see happens inside it. Scroll to play.
Diagram your systems, targets and milestones Before anyone writes code, we map what you already run, mark the target that matters and pin milestones on the way to it. Requirements come out of the fog instead of out of guesswork.
Interview your people and connect the dots We talk to the people who do the work, beside the systems they use. Then we connect what they said: the export ops dreads is the spreadsheet finance re-keys by hand.
Turn every interview into text Interviews are recorded and transcribed. Our speech-to-text tools tag each system, pain point and deadline, so requirements come from people’s own words, not somebody’s notes.
The transcripts become the backlog Tagged lines become backlog items, each placed where the work belongs, with what finished looks like and a link back to the person and minute it came from.
Thousands of AI agents work the backlog dev3lop spawns and orchestrates thousands of AI agents, and our engineers point them at the queue. Every item traces back to a real person, and nothing ships until it is tested and reviewed.
Every cloud, database and API feeds one company Your systems stay where they live, on any cloud or on-prem. Each gets a supply line into dev3lop, and we ship the result end to end: web platforms and desktop apps.
Without the glue, profit stalls Replay the same map with four vendors: one for discovery, one for notes, one for the backlog, one for the build. Every handoff drops context, crews wait on each other, and profit is hard to find.
With it, profit grows over time When one company owns every step, nothing is lost between them. The early turns are an investment; once the supply lines connect, each turn earns more than the last.

Claude #3

Profit Line (transit map)

A calm, flat Mini Metro-style transit map: dev3lop is the one operator. Stations are your systems and people, dashed track is the plan and solid track is built. Interviews meet at one broken handoff, transcripts become 12 numbered tickets, 3,072 agents lay the track, every cloud, database, API and app line runs through one hub, then the map breaks into four vendors and reconnects.

Open full page (opens in a new tab)

Read this version’s story 9 steps

Your business, drawn as a transit map Stations are your systems and people. Dashed track is planned, solid track is built, and every line runs through one interchange: dev3lop. Eight levels, from first diagram to profit.
We map your systems, target and milestones Every project starts as a diagram of the systems you already run. We pin the target, set milestones on the way, and write the requirements down before any code.
We interview your people and connect the dots We talk to the people who do the work. When the CFO and the ops lead describe the same broken handoff, we connect them, and scattered complaints become one clear requirement.
Every interview becomes searchable text Interviews are recorded and transcribed automatically (speech to text). Language processing (NLP) then tags the phrases that matter: systems, pain points, deadlines and asks.
The transcripts write the backlog Tagged phrases become stories with acceptance criteria, each traced to the person and minute it came from. The plan is now twelve buildable pieces.
We orchestrate thousands of AI agents against it dev3lop spawns and orchestrates thousands of AI agents against the backlog. A squad claims each ticket, then builds, tests and reviews it in the order our engineers set. Each finished ticket turns dashed track solid.
Your whole stack runs through one hub Cloud-agnostic and on-prem capable: your clouds, databases and APIs stream in, and web platforms and desktop apps ship out, built end to end by one team.
Split across vendors, the work stalls Hand discovery, notes, backlog and build to four vendors and every handoff drops context. People wait at the gaps, work stalls, and profit stays flat.
One company end to end, and profit compounds When dev3lop runs every stage, nothing is lost between them. The first weeks are an investment; after that, the connected network carries more every week.

Claude #4

Tycoon

An isometric tycoon campaign in 10 levels: each level unlocks one building for one step of the process and a named dev3lop cursor plays it, from mapping your systems to drag-selecting 2,048 agents and piping in every resource. Hard mode splits the board between four vendor cursors so profit leaks, then an illustrative year fast-forwards.

Open full page (opens in a new tab)

Read this version’s story 10 steps

One team runs every step, from the first diagram to profit Your business is the board and dev3lop is the one player at the controls. Each level below is one step of how we build custom software. Scroll to play.
We diagram your systems, targets and milestones Before any code, we map how your systems and teams actually work: where data lives, where it is re-keyed by hand, the target you are aiming at and the milestones on the way. Requirements start here.
We interview your people and connect the dots We talk to the people who do the work, then link what they said. When finance and ops describe the same spreadsheet from opposite ends, that link becomes a requirement.
Every interview becomes text we can search Interviews are recorded and transcribed, voice to text. Language models tag each line with the systems named, the pain described and the deadlines mentioned, so nothing depends on someone’s notes.
The transcripts generate the backlog Tagged lines become backlog items with acceptance criteria. Each one links back to the person and the minute it came from, so every item is traceable.
Thousands of AI agents work through that backlog dev3lop spawns and orchestrates thousands of AI agents. They claim backlog items, then build, test and review in parallel while our engineers direct the work.
Your clouds, databases and APIs feed one core We are cloud-agnostic and on-prem capable. Wherever your systems live, we connect them into one place, including the CRM-to-billing step someone used to re-key by hand.
We build and ship the platform end to end Web apps in React, Vite and Tailwind, Vue.js and Astro front ends, and Electron desktop apps with C++ where speed matters. Once it ships, it starts paying back.
Split across four vendors, profit is hard to generate Hand discovery, notes, the backlog and the build to four different vendors and the work cracks at every handoff. Context gets re-explained, agents wait on someone else’s queue, and profit stalls.
With one team connecting it all, profit grows over time With one company on the whole board, nothing falls through the cracks and each quarter builds on the last. The numbers here are illustrative; the shape is what we build for.

Claude #5On this page

The Build Line (factory)

A Shapez/Factorio-style conveyor factory with a quest log and item hotbar: voice becomes transcripts, transcripts become tickets traced to a person, 2,048 agent bots stream from the tower through the rack into the build bay, and your clouds and databases plug into one line. Then the same factory splits between four vendors and stalls until the glue goes back on.

Open full page (opens in a new tab)

Its 9-step story is the game just below this section. Go to the game

Claude #6

The Build Quest (RPG)

A quest-driven RPG overworld of your company: the dev3lop party (six roles, one team) maps the towns, interviews the people and connects their quotes, types out the transcript under the voice, posts STORY-214, and sends 2,048 agents across the map. Then the same map is replayed as separate vendors (profit leaks at 4 handoffs) and as one team (gold roads, a J-curve).

Open full page (opens in a new tab)

Read this version’s story 9 steps

One team covers every role Mapping, interviews, transcription, the backlog, thousands of AI agents and the build itself all come from one company: dev3lop. Scroll to see how we build your software, one level at a time.
We diagram how your business runs Before any code, we map your systems and the handoffs between them. We expose the target, pin the milestones on the way there and gather the first requirements.
We interview your people and connect the dots We talk to the people who do the work, not only the ones who sign off. When finance and ops describe the same spreadsheet from both ends, that is one problem with one fix.
Every interview becomes tagged text Interviews are recorded and transcribed to text. Our language models tag the systems, pain points and deadlines in the words, so nothing anyone said gets lost.
What people said becomes the backlog Tagged phrases become epics, stories and tasks with acceptance criteria. Each one traces back to the person and the minute it came from.
Thousands of AI agents work the backlog dev3lop spawns and orchestrates AI agents against that backlog, one squad per ticket. Every change passes a review gate run by our engineers.
Your clouds, databases and APIs, connected in one place Cloud-agnostic and on-prem capable. Your systems stream into one platform that we build end to end.
Separate vendors lose context at every handoff One firm maps, another takes notes, another writes tickets, another builds. Each handoff drops context, the departments never connect, and profit stalls.
Connected work grows profit over time When one team owns every step, nothing is lost between them. The build is an investment first, then the time it saves compounds each quarter, and so does margin.

Claude #7

ONE HQ (panel pick)

The judge panel's synthesis: the RTS base with the best grafts from every other pitch — a named dev3lop cursor, one problem thread (the re-keyed CRM export) through every level, inbound vs outbound trunks, and a Glue ON/OFF profit toggle.

Open full page (opens in a new tab)

Read this version’s story 9 steps

How we build custom software, played as a game The base in the middle is dev3lop. Scroll to watch one team go from your first diagram to thousands of AI agents to profit, with every step inside the same company.
Diagram your systems, the target and the milestones Before anyone writes code, we map what you already run: the CRM, billing, the warehouse and the spreadsheets between them. We mark the target that matters and pin milestones on the route to it, so requirements come from what we saw, not from guesses.
Interview the people who do the work, then connect the dots We interview the people beside each system, not only the ones who sign off. When two describe the same problem from opposite ends, we draw the line between them. Here, the CRM export Ops dreads is the spreadsheet Finance re-keys by hand.
Turn every interview into text Every interview is recorded and transcribed by our speech-to-text pipeline. Language processing then tags each system, pain point and deadline people mentioned, so requirements come from their own words, not from someone’s notes.
Generate the backlog from the transcripts Tagged lines become the backlog. Each item lands where the work belongs, as a dashed outline with a definition of done and a link back to the person and minute it came from. Nothing gets built that nobody asked for.
Deploy thousands of AI agents against the backlog dev3lop spawns AI agents by the thousand, and our engineers direct them: which item, in what order, what counts as done. Nothing ships until it is tested and reviewed. The first fix lands here: the hand-keyed route becomes a nightly sync.
Connect every system to one hub, on any cloud or on-prem Your systems stay where they live, on any cloud or on-prem. Each one gets a supply line into dev3lop, and one line carries out what we build: web platforms and desktop apps.
Without the glue, work falls through the cracks Now play the same map with four vendors: one for discovery, one for notes, one for the backlog, one for the build. Context drops at every border, crews wait on each other, and in this demo the nightly sync stalls at 40%. Profit barely moves.
With one company, profit grows over time Put the glue back and nothing falls between steps. The early turns are an investment; once the lines connect, each turn builds on the last. The chart is illustrative, not client data.

Codex · 3 versions, built outside the repo as standalone three.js pages

Codex C1

Every moving part

Codex iteration 1: an exploded precision watch you can drag and assemble, with a guided six-phase story (Discover, Listen, Translate, Orchestrate, Deliver, Compound) and the cloud, data and stack names streaming into one shared context.

Open full page (opens in a new tab)

Read this version’s story 6 steps

Start with the whole picture. Before we build, we map your systems, reveal the dependencies, and define what success looks like. Every requirement has a place. Every milestone has a purpose.
Different voices. A shared understanding. We interview the people behind the process. Connecting their needs reveals the same problem from different angles—and the opportunities hiding between departments.
Conversations in. A clear backlog out. Voice-to-text captures the conversation. NLP connects systems, pain points, and requirements. We validate the findings and turn them into stories with clear acceptance criteria.
Thousands of agents. One shared direction. DEV3LOP orchestrates specialized AI agents against the validated backlog. Shared context connects building, testing, and review. Our engineers direct the work and approve the releases.
Your systems. Working as one. We build the complete platform: web experiences, APIs, data pipelines, and desktop applications. Your choice of cloud or on-premises infrastructure. One company connects every layer.
Less friction. More room for profit. Disconnected parts create rework and operating costs. One connected delivery process reduces those handoffs, shortens the path to value, and creates capacity for profit to grow over time.

Codex C2

Inside every moving part

Codex iteration 2: every step opens its own animated 3D process scene lifted out of the watch — interviews converging on a shared requirement, a typed transcript with NLP extraction into backlog item INT-014, four clusters of 512 agents with a human release gate, systems converging on dev3lop, and a spatial growth chart you can disconnect.

Open full page (opens in a new tab)

Tells the same 6-chapter story as Codex C1; what changes is how it looks and plays.

Codex C7

Living architecture · final

Codex iteration 7, its latest: adds a plain-language guide for all 32 buildings (what each does, when it helps, a concrete example) and opens in exploration mode with an opt-in tour.

Open full page (opens in a new tab)

Read this version’s story 6 steps

Start with what you know. A problem, an idea, or work already underway is enough. We help clarify what to build and choose the planning tools that are useful for your project.
Hear the people. Understand the work. Conversations can reveal what people need and where work gets stuck. We choose who to involve based on the problem. The departments shown are examples.
Turn what you know into work we can build. Ideas can come from a conversation, written notes, or existing documents. Voice-to-text and language analysis are optional tools that help us capture and organize them.
Human direction. AI where it helps. Our engineers can use AI agents to assist with planning, coding, testing, and review. We choose the support that fits the project and keep people responsible for decisions.
Built around what you need. Your solution might be a website, a desktop app, an integration, or a complete platform. We select the technology and hosting that fit. You do not need every tool shown.
Less repeated work. More room to improve. Connecting the right pieces can reduce manual work, shorten delays, and free up time. We look for the improvement that matters to your business and evaluate what changes.

How dev3lop builds

One line from conversation to profit

Play through how we turn your people’s conversations into connected software, and why keeping every step on one line is what pays off.

Skip the game Jump to the payoff

Production statistics Illustrative, not client data

Separate vendors One line (dev3lop)

How we build
Conversations in, working software out
Every build we run works like a production line: your people’s conversations go in, working software comes out, and profit is the point. Scroll to watch the line get built, one station at a time.
Step 1 · Diagram
We map your systems before we build anything
We diagram how work moves through your CRM, spreadsheets and billing today, name the target, pin the milestones and gather the requirements, before any code is written.
- CRM
- Spreadsheets
- Billing
- Target
- Milestones
- Requirements
Step 2 · Interviews
We interview your people and connect what they tell us
Requirements live in people’s heads, so we interview the ones who do the work. Then we connect the dots: when finance and ops describe the same spreadsheet from opposite ends, that link becomes a requirement.
- Finance
- Ops
- Sales
- IT
- Support
Step 3 · Transcription
Every interview becomes searchable text
Each conversation is recorded and transcribed. Natural-language processing tags the systems, pain points, deadlines and asks, so nothing depends on someone’s notes.
“Every Monday I export the CRM to Excel and re-key it into billing before month-end.” Example · Interview 3 · Ops lead · 00:14:32
Step 4 · Backlog
The transcripts become the backlog
Tagged phrases become epics, stories and acceptance criteria. Every ticket traces back to the person and the minute it came from, so the backlog is what your people asked for.
STORY-214 Nightly CRM → billing sync Example · Acceptance: no rows re-keyed by hand at month-end · Source: interview 3, 00:14:32
Step 5 · AI agents
Thousands of AI agents work the backlog, orchestrated by us
dev3lop spawns thousands of AI agents against the backlog. Each one claims a ticket, builds it, tests it and hands it back. Our engineers set the priorities and approve what ships.
Each dot in the scene is one agent. The tower is the one coordinator; green means tested and handed back.
Step 6 · One company
All of it runs inside one company, wired to your systems
Your clouds, databases and APIs plug straight into the line, in the cloud or on your own servers. Out come web apps and desktop software, built end to end.
Cloud & on-prem
- AWS
- Azure
- GCP
- Netlify
- DigitalOcean
- On-prem
Databases
- Postgres
- Neon Postgres
- SQL Server
- MySQL
- SQLite
- SQL
APIs
- REST
- GraphQL
- Webhooks
- Streams
What we build end to end
- React
- Vite
- Tailwind
- Vue.js
- Astro
- Electron desktop apps
- C++
Without the glue
Split the same work across four vendors and it stalls
One vendor for discovery, one tool for notes, another for the backlog, a separate shop for the build. The same work piles up at every handoff, context leaks out, and profit stalls.
With the glue
Keep it on one line and profit compounds
Put the line back together and work flows end to end. After a short build-up, the time saved at every handoff adds up month over month, and so does margin.
The chart is illustrative, not client data.
Start your blueprint