Loading articles…
Field notes for building a business that can move without you.
We write from the intersection of operating systems, software, sales, marketing, and leadership—for owners building a more capable company.
Operating systems
Start With the Business Outcome, Not the Software
The best place to start with a new tool isn't its feature list. It's the work your business is trying to accomplish—and the people responsible for getting it done.
- Author
Everett Bellingham- Published
- Reading time
- 5 min read
Contents
A client asked me for help getting started with Telos this week. They wanted to use it but weren't sure where to begin, so they asked me to walk them through what to do.
We could have started with a tour of the software: what to set up, which features to use, and how everything fit with the tools they already had.
Those are reasonable things to want help with. But they are not where I like to start.
When we begin with a list of features, it is easy to build a system around what the software can do instead of what the business actually needs. Before long, the team is learning screens, configuring fields, and maintaining processes that might not help them reach the results the business actually needs.
I would rather start with a different question: What are you trying to accomplish?
Then we can work out where software helps, where people need to make decisions, and what can stay as it is.
Start with the work in front of you
So I asked what was happening in their business and what they wanted to accomplish next. As we talked, the immediate goal became clear: fill a new program by reaching people who already had a relationship with the business.
That gave us a much better starting point than a feature tour. To understand the work around that goal, we could ask questions like:
- What is the program, and who is it for?
- Which people are you inviting?
- What needs to be written or prepared before you reach out?
- How will you keep track of people who express interest?
- What does the team need to do next, and who is responsible?
Once we had that context, the technology choices were easier to make. A sales pipeline could help the team track individual conversations. A project could hold the work involved in getting the program ready. Marketing copy could be kept in a place where the team could find and revise it.
We did not need to use every feature. We needed a useful starting point for this particular piece of work.
Software should fit the business, not the other way around
I work with people who have already put a lot of effort into the way their businesses run. They have relationships, processes, documents, and tools that make sense to them. Some parts work well. Other parts are frustrating, but they exist for a reason.
Introducing a new system should begin with understanding that reality. It is worth asking what needs to change, what needs to be preserved, and what the team can reasonably take on right now.
In the program-launch conversation, the client already had a system they could use to send their marketing emails. The approach we discussed did not require abandoning it on the spot. We could organize the work and copy in Telos while continuing to use the existing tool for the sending portion.
That may mean some manual work remains for a while. I would rather be honest about that than pretend an integration is complete when it is not. A system that helps with the current goal and fits the team's situation is more valuable than a theoretically perfect setup nobody is ready to use.
AI is more useful when it has context
Another part of the conversation was about the effort involved in keeping several pieces of copy aligned. If you change the offer in one document, which emails or scripts also need to change? Who remembers where the latest versions live?
AI can help with that work, but it needs context. If the details are scattered across files and conversations, a person still has to gather them, explain the background, and carry the results to the next place.
The way I described it on the call was that Telos can be the brain holding the business context, while an AI assistant helps make requested changes. That is a useful way to think about it—not because the AI should make every decision, but because the person doing the work should not have to reconstruct the entire project every time they ask for help.
For example, a team could ask an assistant to review the marketing copy for a project after the offer changes and propose updates. Someone still needs to check the suggestions, decide what is right, and make sure the final message sounds like the business. The AI helps carry the work; the team remains responsible for the judgment.
A practical way to begin
If you are considering a new tool—or wondering whether you are getting enough value from one you already have—pick one piece of work your team is actually trying to move forward.
- Name the outcome. What are you trying to accomplish, and how will you know you have made progress?
- Describe the work as it happens today. Who is involved? Where does information live? Where do people get stuck or repeat themselves?
- Choose the smallest useful change. It might be a shared project, a clearer follow-up process, or a better place to keep the information people need.
- Use the tools that fit. A new system does not have to replace every existing tool immediately. Use what helps the work move forward.
- Try it with the people doing the work. See what helps, what creates friction, and what needs to change. Then adjust.
The goal is not to build the most impressive configuration. It is to make the work easier to understand, easier to carry forward, and more likely to get the result you were after.
The outcome is the point
I enjoy working with technology. I also know how easy it is to get excited about what a tool can do.
But a feature is only useful when it helps someone accomplish something that matters to their business. Sometimes the right answer is to use more of the software. Sometimes it is to use less, keep an existing tool, or pause and clarify the work first.
That is how I want to approach Telos and the support we provide through Accelerator OS: understand the outcome, work alongside the people responsible for it, and use technology to help them get there.
