# Before buying software, hiring, or building something custom to fix a process, did you document how it actually worked first? — retained record

> Retained reddit record from reddit:smallbusiness.

Canonical: https://highsignal.app/data/records/679ca5d86f0a5820

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:smallbusiness)  published 2026-10-09 13:03 ingested 2026-10-10 02:36

[original source ↗](https://www.reddit.com/r/smallbusiness/comments/1x1kt90/before_buying_software_hiring_or_building/)

## retained text



```
Asking because I think this step gets skipped a lot, and I'm genuinely not sure it's always a mistake to skip it.

The usual options for a messy process are some mix of new software, a new hire, or a custom build. Each can work. But when it goes sideways, the problem often isn't the choice itself. It's that nobody captured how the work really ran first, so the software got set up around the official process, the new person learned by trial and error, or the build was scoped from an incomplete picture.

On the other hand, documenting everything first takes time, and sometimes you only find out how a process really works once you try to change it.

For people who've been through this: did you map the process first, or figure it out as you went? Which worked better?
```



document fetched 2026-10-10 00:32 · canonical https://reddit.com/r/smallbusiness/comments/1x1kt90/before_buying_software_hiring_or_building
