Glossary
The words we build with.
Plain-language definitions of the terms we use across our site, our products, and our partner work.
- AI agent
- Software that can hold a conversation, make decisions, and complete a task on its own — like answering a restaurant's phone and taking the order without a human stepping in.
- Build scope
- The written boundary of a first release: what ships now, what waits, and what we deliberately won't build. Saying no in writing is what keeps a first version small enough to prove.
- Co-build
- A partnership where we build the first version of a product together with a founder — strategy, design, and engineering from one team — structured so the founder keeps ownership.
- Conversational app
- An app you use by talking or typing to it instead of clicking through screens. FlowCP is our platform for building and operating these.
- First version
- The smallest release that can earn real usage, trust, and revenue. Not a demo, not the full vision — the slice that proves the product deserves to exist.
- Operating layer
- Everything around the code that keeps a product alive after launch: onboarding, support, metrics, and the feedback loop. We build it together with the product, not after it.
- Pilot
- A limited, real-world deployment used to prove a product works with actual users before a wider rollout.
- Portfolio product
- A product we build and operate rather than hand off to a client. It has to earn its keep with real customers, real revenue, and real maintenance.
- Positioning
- The short story of who a product is for, what it replaces, and why it's worth paying for. If it takes more than a few sentences, it isn't done.
- Product studio
- A team that designs, builds, and operates products end to end — strategy, design, engineering, and operations under one roof.
- Prototype
- A clickable model of a product used to test the riskiest workflow before engineering begins, so people can react to something concrete instead of a pitch.
- Workflow audit
- A structured look at how work actually happens in a business — the spreadsheets, messages, and handoffs — to find the repeatable steps software could take over.