How to Document Processes in an Integration Business (Without Over-Engineering It)

To document processes in an integration business, you need to start with clarity. Step back and map how a project moves through your company, ask your team where it breaks, and fix the one or two biggest pain points first. Write each process for a competent person, solve for today's problems, and choose the path forward or decide on software only after the process is clear.

That's the approach Jason Sayen, founder of I Am Sayen, uses with integrators. Sayen spent 10 years at JL Audio watching assembly lines before becoming a process architect for the CI industry. He walked through his framework on episode 12 of 1NSIGHTS.

What do undocumented processes cost an integrator?

More than most owners realize, because the cost is invisible. Sayen cites a Grammarly study estimating that miscommunication costs companies about $12,506 per employee each year. For a 10-person AV company, that's roughly $125,000. At a 10% net operating margin, you'd need about $1.25 million in additional sales to make up for it.

The waste shows up in familiar ways. An $18,000 motorized lift ordered wrong sits in the warehouse. A client's $20,000 check sits on the CFO's desk because nobody attached an invoice.

When Sayen asked that sales team why, he got three answers: the client paid on a Friday, a salesperson didn't know invoicing was their job, and a new hire had never been trained. None of that required a thick SOP manual. It required clarity among the people involved.

Healthy margins let integrators run inefficiently and still make money. Sayen's point is that cutting that waste in half is often easier than selling more.

Where should an integrator start documenting processes?

With your team and a whiteboard. In a live poll during the episode, 53% of attendees said their documentation exists but is outdated or scattered. Sayen's starting point works whatever your situation:

1. Assign an owner. Documentation goes stale when nobody owns it. Most companies have a process-minded person who would welcome the job.
2. Map your phases. Write the stages every project moves through: proposal, project kickoff, production (pre-wire, trim, final) and service.
3. Ask where it breaks. Hand out sticky notes and have the team mark the biggest pain points. Keep the conversation on what's breaking, not who.
4. Look upstream. Problems that surface in production usually start earlier. Twenty change orders on a job often trace back to a weak scope of work or handoff.
5. Fix one or two. Get them into a routine, then move to the next.

Sayen's core mindset comes from manufacturing: think of your business as a production line with stage gates. Custom work will always have exceptions. Structure lets you manage them instead of being managed by them.

How do you map a single process?

Once you've picked a pain point, Sayen unpacks it in five layers. The structure keeps the session focused, and most processes can be mapped in an hour.

• Bookends: How does it start, how does it stop, where does it get stuck? Example: starts when the client signs and pays; ends when product is ordered and the job is scheduled.
• Steps: What happens in between, with what tools and checkpoints? Example: review scope, plans and equipment list in a kickoff meeting.
• Standards: Why do we do it this way? Example: every project gets a kickoff before any product is ordered.
• Roles: Who is responsible? Example: salesperson, project manager, designer.
• Systems: What software supports it? Example: proposal tool, project channel, scheduling.

Systems come last on purpose. Many owners try to solve process problems by adding software, but software only makes a clear process more efficient.

How detailed should an SOP be?

Detailed enough for a competent person, and no more. Sayen sees two common ways documentation gets over-engineered:

• Writing for someone with no skills. Separate skills training from job training. An SOP for invoicing should show a bookkeeper who knows QuickBooks how your company invoices, not teach QuickBooks.
• Solving future problems. Write for today's constraints. When the business changes, the process owner updates the document.

Will new software fix broken processes?

Usually not. Sayen's view is that there's no magic software, only a magic process. Without a clear process, a new platform exposes the gaps. File storage doesn't connect to your current system, accounting sync only runs one way, or project communication ends up back in group texts.

Before buying, ask how each step of your process would actually work in the new tool. One small integrator he worked with thought it needed project management software. It already had Slack and simply wasn't using it well. After setting up a channel per project and banning project texts, the team felt relief within three days.

Clear processes pay off in two more ways:

• AI needs context. Sayen treats AI as a digital employee. Documented processes are exactly the context AI tools and agents need to be useful.
• They make the business sellable. A company that can run without its owner is transferable. In a second live poll, most attendees said their business would keep running for 30 days without them, but only by leaning on one other key person.

Watch the full conversation

Jason Sayen | When it’s All in Your Head: The Cost of Undocumented Operations

1NSIGHTS Podcast

0:000:00

Sayen and Jason Griffing, OneVision's Director of Product, also walk through applying the framework to the project-to-service handoff.

About 1NSIGHTS
1NSIGHTS by OneVision explores how integrators, operators and industry leaders think, build and adapt in a fast-changing custom integration landscape. Recorded live and shaped by audience questions, each episode goes past surface-level trends to the real decisions and trade-offs behind growing smarter and staying competitive. Explore all episodes →