Tell us what needs to change. We’ll work out what it takes.

You know something in the business needs to change — an application nobody can safely touch, a process running on spreadsheets, an idea with no plan, a platform with no one to own it. Describe it in your own words. We work out what it takes, build it, and stay accountable for it afterwards.

You know something needs to change, but not what it takesManual work is taking time away from higher-value workTechnology matters to the business and nobody inside it owns it
Make Directory Development
booting|
guest@make-directory:~$ ls ./what-we-solve
guest@make-directory:~$ tree ~/environments

where this usually starts

Your industry matters less here than the situation you are in.

unowned-software/

Software nobody owns

The application still runs the business, but the developer who built it is gone and the same problems keep coming back.

|-- legacy-app.ts
|-- undocumented-deploy.sh
|-- access-inventory.md
`-- risk-register.md
disconnected-systems/

Systems that do not talk

Tools were bought one at a time, so staff move data by hand and the spreadsheets in between became the real system of record.

|-- integrations.ts
|-- sync-jobs.py
|-- reporting.tsx
`-- manual-steps.md
cloud-and-operations/

Cloud and operations drift

Infrastructure, backups, and vendor accounts accumulated over years, and no one is confident about what would happen in an outage.

|-- infrastructure.tf
|-- backups.md
|-- monitoring.ts
`-- vendor-map.md
idea-without-a-path/

An idea with no path

Everyone agrees it should exist. Nobody can say what it would take, what it would cost, or what it should be built on.

|-- requirements.md
|-- unknowns.md
|-- phases.md
`-- first-release.md
guest@make-directory:~$ cat ./our-work.md
guest@make-directory:~$ cat ./how-we-work.md

understand -> recommend -> execute -> own

A practical path from unclear problem to owned system.

01

Understand

We learn the systems, the workflows, and the constraints before recommending anything.

02

Recommend

You get a plain-language read on what should change, in what order, and what it costs.

03

Execute

We build in working increments, with the decisions and tradeoffs kept visible.

04

Own

We keep the system documented, maintained, and improving as the business changes.

guest@make-directory:~$ cat ./ways-to-work-with-us.md
guest@make-directory:~$ cat ./fit-check.md

where we do our best work

You will get the most from us when software carries real weight in the business.

FITYour business depends on software but cannot justify a full internal team
FITTechnology affects your operations, revenue, risk, or customer experience
FITThe work continues past a launch date, and someone has to own the system
guest@make-directory:~$ ls ~/capabilities
guest@make-directory:~$ ls ./insights | head -3
guest@make-directory:~$ mkdir ./what-needs-to-change

ready when you are

Tell us what is not working. We will tell you what it takes.

The customer friction, the slow internal process, the half-built idea, the unstable infrastructure, the system nobody owns — start with whichever of those you can see from where you sit. Sorting out what it actually needs is the first thing we do.

Not sure what you need?

Most people are not, and it is a normal place to start. An assessment gives you a documented read on what exists, what is at risk, and what it would take to fix — for less than a month of the smallest ongoing plan, and it is yours to keep whether or not you continue with us.

Start an Assessment