Stage — not production
facilist
Jeffrey Duncan, founder of Facilist

Why I built Facilist

My wife works in real estate. When she walks a home to get it ready for sale, she notices things room by room: replace that outlet, patch this wall, repaint that trim. Notes and photos capture pieces of it, but they separate the task from its context. Later, she has to reconstruct which photo goes with which note and, most importantly, where each thing actually is. Then whoever receives the list has to interpret it all over again.

I hit the same wall while walking a newly built office looking for unfinished work. Spotting a problem takes seconds. Documenting it well enough for someone else to find it is the expensive part. “There’s a drywall issue here” is easy. Explaining where here is takes longer than finding the issue did. Multiply that across dozens of items, and the documentation becomes a job of its own.

Facilist collapses all of that into the moment of discovery. Point your camera, say what the next person needs to know, and the photo, your voice, and a transcript become one item — the what, the where, and the context captured while they’re still obvious instead of reconstructed later.

When you’re done, hand off the finished list with a single link. The person receiving it can get to work without asking you a thing. No app to install. No account to create. Nothing to study.

Point it out. Capture the context. Hand it off. Done.

I’m building Facilist small and careful on purpose. Your list lives behind a private, unguessable link you can revoke at any time. Your recordings stay yours. And the product does one thing — make lists that don’t need to be explained — as well as I can make it.

— Jeffrey Duncan, bug-finder and problem solver · Utah, USA · LinkedIn · feedback@facilist.org