> ## Content Index > Fetch the complete content index at: https://valdivya.com/llms.txt > Use this file to discover other available public pages before exploring further. # Developing an Operational Strategy: Working In vs. Working On Your Business - URL: https://valdivya.com/developing-an-operational-strategy-working-in-vs-working-on-your-business/ - Published: 2026-10-01T12:00:44.000Z - Updated: 2026-10-01T12:00:45.000Z - Description: Small business owners are capable of connecting every operational dot themselves. Here's why that's not always the right call, and what it costs when you do. · Read the post → - Author: Jesse Hormachea - Tags: all --- ## Key Takeaways - **Every small business runs on process, whether it's written down or not.** What works fine solo becomes a liability the moment you hire. - **Systems like a CRM, Jira, or an HRIS only work if they're connected to your actual process**. - **Connecting the dots yourself costs you something.** Every hour spent on systems and process is an hour not spent building, selling, or leading. - **This is the founder's bottleneck:** you're capable of doing this work, but doing it isn't why you started the company. - **A tech inventory, clear must-have features, and a real trial run are a starting point**. Then the real work begins. --- Most of my engagements this year have started with some variation of the following: > “I’ve been doing it but I need something off my plate” > “It’s on my list and I am just never getting to it” > “I can do this work and I know it’s important but I need help” These are all very capable, smart people, but the reality is there are only so many hours in a day. There is also only so much space in a brain. Small business people are used to wearing all the hats. Most of us thrive in that environment, but the best small business owners know how to work in their zone of expertise. **Just because you can do something, doesn’t mean you should.** The operating system for your business shouldn’t be pieced together with duct tape and glue. No matter how small or big your organization is, you need someone working to solidify and automate the process you have. It’s the only way for small businesses to move forward. ## Every Business Runs on Process Process isn’t a dirty word. The reality is everyone has a system they work within, even if it isn’t written down. People don’t want to admit it, but whatever you’re doing day to day is the process. It works fine when you’re a one-person operation, but suddenly, that second person comes in the door and it’s all in your head. This is where the challenges with scaling start to compound. That’s been the most interesting and unexpected part of my work this year. Strategic and visionary individuals who want to grow their organization of one have worked with me to lay the groundwork to bring on more people. They recognize they have process and a lot of it. They want to preserve how they do business and the name they’ve built over years when that new hire starts. ## Every organization needs an operational strategy. Now that we’ve agreed that a process exists in every org, it’s now important to figure out how systems and people integrate within that system of work. For sales, that means a CRM. For projects and operations, that’s a task management tool like Jira. For HR, it’s the HRMS or HRIS. You get it. Each of these requires knowledge of the business, the workflows, the people and the technology you have to connect it all. You can hire an expert in one area, but they won’t be well equipped in all. Good luck getting real support from the product providers. You need an operational strategy across your organization. As a founder, you’re capable of connecting all these dots. The minute you do, you’re taking your eye off your mission. Something will suffer. Maybe building the product, closing the deals, or leading in general. **This is the founder’s bottleneck.** It's the difference between working *in* your business vs working *on* your business. These things are all fun to figure out and help the team start using them, but it’s not why you built your company. ## How to Get Started Here are some ideas to begin the discovery work, but remember, the systems integration, enabling the team and the time are where the real work is. ### Take a Tech Inventory Figure out what systems you already have. Does anything you currently pay for already do what you’re looking for a new product to do? Does it have an add-on module? Do you want to auto-provision accounts? Do you want to do single sign-on (SSO)? This is more challenging than it sounds because one of the hardest parts is having the technical knowledge to close the gaps on what is possible with the existing tools, frameworks, and the outside knowledge to know what’s available. ### Identify your 3 Must-Have Features Any product is going to have its pluses and minuses. Nothing is perfect. Unless you’re going to vibe code your own solution and maintain it, you’ll have to live with something not being exactly to your spec. Understand what’s most important to you before you make a purchasing decision. This also may feel deceptively simple, but the reality is when it’s your business, all of the steps feel important. It’s hard to let go of something that feels like it’s working. **It’s easier to keep a broken system because it’s familiar.** The outside perspective helps push what you do forward. ### Start a Trial Every product will have a trial period. Take advantage of it. Get a few trusted people in there. Especially ones that don’t mind disagreeing with you. This will be challenging. You’re under a time crunch with a trial to configure real use cases, get people in there, and run real workflows. All within a 7, 14, or maybe even 30-day trial. It’s never enough time. These ideas are the most basic starting points to help you get going. If this feels like something you want off your plate, I’m here to get you time back and refocused on the reasons you built your company. [Help Me Get Back On Mission](https://valdivya.com/contact/)