Is Your Business Ready to Scale? | Tech Operational Readiness Assessment

Step 1 of 10

About Your Business

Tell us a bit about your company so we can tailor the results to your situation.

Briefly describe your business -- what you sell or deliver, and roughly how many employees you have.

What is your approximate annual revenue?

Under $5M$5M - $15M$15M - $50M$50M - $100M+

How would you describe your company's growth over the last 3 years?

Flat or decliningSlow, steady growth (5-15% per year)Strong growth (15-30% per year)Rapid growth (30%+ per year)

What is your biggest frustration with how your business operates today?

Everything takes too long and requires too many peopleWe can't get reliable information to make decisionsWe keep making the same mistakes over and overWe can't grow without adding headcount proportionally

Manual Processes & Human Error

These questions look at how much manual work is required to keep your operations running day to day.

How does information move between your core business systems (e.g., CRM to accounting, orders to fulfillment, HR to payroll)?

People copy-paste or re-type information from one system into another. It happens all day, every day.Some connections exist, but most handoffs between systems involve someone exporting a file and importing it elsewhere.Most major systems are connected, but a few gaps remain that require manual work.Our systems are integrated end-to-end. Data flows automatically between them with minimal manual intervention.

When your team processes an order, onboards a new customer, or completes a core transaction, how many different screens or applications do they touch?

I honestly don't know -- no one has mapped it out.5 or more systems. It's a lot of clicking around and people have cheat sheets taped to their monitors.3-4 systems, with some overlap. People know the routine but it takes a while.1-2 systems handle most of it. The workflow is streamlined and takes minutes, not hours.

How often do you discover errors -- wrong prices, duplicate entries, missed steps -- that trace back to someone manually entering data?

Regularly. We find errors weekly and suspect there are more we don't catch.A few times a month. Usually someone catches it before it reaches the customer, but not always.Occasionally. We have some checks in place, but they are mostly human eyeballs reviewing things.Rarely. We have automated validation and alerts that catch problems before they propagate.

How are approvals handled for things like purchase orders, discounts, refunds, or time-off requests?

Verbally or via email/text. There's no formal trail and things fall through the cracks.Email chains or shared spreadsheets. It works, but finding the history of who approved what is painful.We have some approval workflows in our software, but many exceptions still go through email.Structured approval workflows are in place with notifications, escalation rules, and a clear audit trail.

If you had to double your transaction volume tomorrow with your current team, what would happen?

We would drown. Our processes are barely keeping up with current volume.It would be ugly. We'd need to hire immediately and would make a lot of mistakes in the meantime.We could handle some increase, but quality would suffer and turnaround times would stretch.Our processes are largely automated. We could handle significantly more volume without proportional headcount increases.

Back Next

Tribal Knowledge & Key-Person Risk

These questions explore how dependent your business is on specific individuals and undocumented know-how.

If the person who knows your most critical business process took a two-week vacation starting tomorrow, what would happen?

Honest answer? That process would stop or break. No one else really knows how it works.Someone would muddle through, but they'd need to call or text the person on vacation for help.A couple of people know the basics, but nuances and exceptions would get handled wrong.It's documented and cross-trained. Multiple people can run it independently without disruption.

How long does it typically take to get a new employee in an operational role fully productive?

6+ months, and honestly they never learn all the tricks and shortcuts the veterans know.3-6 months. There's a lot of "watch and learn" and informal training.1-3 months. We have some documentation and structured onboarding but it could be better.Under a month. We have documented procedures, training materials, and a structured ramp-up plan.

How are your standard operating procedures and process documentation managed?

We don't really have formal documentation. Knowledge lives in people's heads.Some things are written down, but the documents are outdated, scattered across shared drives, or incomplete.Most key processes are documented, but keeping them current is a constant struggle.Documentation is centralized, version-controlled, regularly updated, and actively used by the team.

When someone leaves your company, how much operational knowledge walks out the door with them?

A lot. We've lost people before and it took months to recover. Some things were never fully reconstructed.More than we'd like to admit. The replacement usually discovers gaps for weeks or months after.Some, but we try to do knowledge transfer during the notice period. It helps but isn't perfect.Very little. Our processes, contacts, and institutional knowledge are in systems, not in individuals.

How many critical vendor relationships, passwords, or account credentials are known by only one person?

Many. If that person left, we'd have a serious problem accessing key accounts and services.A few important ones are single-person knowledge. We know it's risky but haven't fixed it.Most are shared or documented, but there are probably a few gaps we haven't identified.All critical credentials are in a shared password manager, and vendor relationships have multiple contacts on file.

Back Next

Data Silos & Disconnected Systems

These questions reveal how well your systems talk to each other and whether you have a single source of truth.

If your sales team and your operations team both pulled a report on last month's revenue, would the numbers match?

Almost certainly not. Different teams use different systems and define metrics differently.They'd be in the ballpark, but the details (timing, categorization, inclusions/exclusions) would differ.They'd match at the top level, but drill-down details might diverge because of how each system categorizes data.Yes. We have a single source of truth for financial data that all departments reference.

How many times is the same customer or vendor information entered into different systems across your organization?

I don't know -- we've never mapped it. It's probably more than we think.The same contacts exist in 3+ systems (CRM, accounting, project management, email marketing) and they're often out of sync.We have some sync between major systems, but duplicates and mismatches still crop up regularly.Customer and vendor data lives in one master system and syncs to others automatically. Records are clean and consistent.

How connected are your front-office systems (sales, marketing, customer service) to your back-office systems (accounting, fulfillment, HR)?

They are completely separate. Someone is always the "bridge" between them, manually relaying information.Loosely connected through exports, shared spreadsheets, or one person who enters data in both places.Some automated connections exist (e.g., CRM to accounting) but major gaps remain.Well integrated. When a sale closes, the downstream processes (invoicing, fulfillment, etc.) are triggered automatically.

When a customer contacts you, how quickly can anyone on your team see that customer's full history (purchases, support tickets, invoices, communications)?

They can't. They'd need to check multiple systems and ask around.If they know where to look, they can piece it together in 15-30 minutes across different systems.Most of the history is in the CRM, but some things (invoices, support tickets, contracts) require checking other systems.Within seconds. We have a unified customer view that pulls from all relevant systems.

How do different departments share information with each other on a day-to-day basis?

Mostly through hallway conversations, phone calls, text messages, or walking over to someone's desk.Email chains, shared drives with files, or messaging apps like Slack/Teams -- but finding things later is hard.Collaboration tools are in place, but departments still maintain their own separate systems and spreadsheets.We have shared platforms with structured data and defined handoff points between departments.

Back Next

Reporting & Visibility

These questions look at how easy it is to get answers about how your business is performing.

If I asked you right now, 'How is the business doing this month compared to last month?' -- how would you get that answer?

I'd need to ask 2-3 people to pull numbers from different systems. It would take a day or more.I could get a rough answer from a monthly report that someone prepares, but it's usually a week or two behind.I can check a dashboard, but it only covers part of the picture (e.g., revenue but not costs, or sales but not fulfillment).I can open a dashboard right now and see real-time performance across key metrics -- revenue, margins, pipeline, operations.

How are your most important business reports created?

Someone manually pulls data from various systems into a spreadsheet each week/month.Semi-automated -- some data feeds in automatically, but a lot of manual cleanup and formatting is still needed.Reports are mostly automated, but we still need someone to verify accuracy and handle exceptions before sharing.Fully automated dashboards that update in real time. No manual intervention needed for standard reporting.

When you need to make a major business decision (pricing change, new hire, market expansion), what data do you rely on?

Mostly gut feel and experience. We don't have reliable data to back up decisions.We have some data, but gathering it takes so long that decisions are often made before the analysis is ready.We pull data for major decisions, but it requires custom analysis each time -- nothing is pre-built or standardized.We have pre-built reports and dashboards for our most common decision types. Data is available when we need it.

How confident are you that the data in your systems is accurate and up to date?

Not very. We've found enough errors that we don't fully trust what's in there.It's probably mostly right, but we don't have a good way to verify. We work around known issues.Reasonably confident for core data (finances, customer records), but secondary data can be stale or incomplete.Very confident. We have data validation rules, regular audits, and clear ownership of data quality.

Back Next

Customer Experience & Response Time

These questions examine how your operations affect the experience your customers have with your company.

When a new lead or customer inquiry comes in, what happens?

It depends on who sees it first. There's no standard process and things sometimes fall through the cracks.It usually goes to one person's email inbox. If they're busy or out, it waits.Leads get into our CRM, but follow-up timing and messaging is up to the individual rep.Leads are automatically captured, assigned, and follow-up sequences are triggered based on defined rules.

Can you tell, right now, how many open customer requests or issues are unresolved and how long they've been waiting?

No. Requests come in through multiple channels and there's no central view.Only if I ask the team. They probably know their own queue but there's no aggregate view.We have a ticketing or tracking system, but not everything goes through it. Coverage is partial.Yes. All customer requests are tracked in one system with SLAs, aging reports, and escalation triggers.

How consistent is the experience a customer gets from your company, regardless of which employee they interact with?

Very inconsistent. It depends entirely on who they get. Some people are great, others... less so.Somewhat inconsistent. Senior people handle things well, but newer employees struggle to match the quality.Mostly consistent for standard interactions, but complex or unusual situations are handled differently by different people.Highly consistent. We have defined processes, templates, and quality standards that everyone follows.

How do you currently follow up with customers after a sale, delivery, or service engagement?

We don't, unless they reach out to us with a problem.Sporadically. It depends on the rep or account manager remembering to check in.We have some follow-up processes (surveys, check-in calls), but they're manual and inconsistent.Automated follow-up sequences are triggered at key milestones, with escalation paths for issues.

How long does it take your team to produce a quote, proposal, or estimate for a customer?

Days or even a week. It requires gathering information from multiple people and systems.1-2 days. The right person can do it, but it involves manual lookups for pricing, availability, and specs.Same day for standard requests. Complex or custom quotes still take longer.Minutes to hours, even for complex requests. Pricing, configurations, and templates are systematized.

Back Next

Scaling & Growth Bottlenecks

These questions look at whether your operations can keep up as your business grows.

Over the past 2 years, has your headcount grown faster than your revenue?

Yes, significantly. We keep adding people but revenue isn't growing proportionally.Roughly at the same rate. We need to hire to handle more volume.Revenue has grown a bit faster than headcount, but it's tight.Revenue has grown substantially faster than headcount. We've gotten more efficient as we've scaled.

Which of these statements best describes your experience with growth?

Growth has actually created more problems than it solved. We're busier but not more profitable.We've grown, but it's been painful. Every new level of volume breaks something.We've managed growth, but it's required constant firefighting and workarounds.Our operations have scaled smoothly. Growth has made us more efficient, not less.

If a major new customer or contract landed tomorrow -- say, 30% more volume -- could your current operations handle it?

Absolutely not. We're at capacity now and struggling with current volume.Only if we hired immediately. Our processes can't absorb more without more people.We could handle it temporarily, but quality and turnaround would suffer until we adjusted.Yes. Our systems and processes have headroom. We'd need some new people but not proportionally.

How do you handle seasonal peaks, spikes in demand, or project surges?

Everyone works overtime, things get missed, and we apologize a lot. We dread busy season.We bring in temporary staff, but ramping them up takes too long to actually help during the peak.We have some playbooks for busy periods, but key processes still bottleneck on a few people.Our processes are designed for variable volume. Automation handles the load increase, not extra bodies.

Back Next

Compliance & Risk

These questions examine how well your organization manages regulatory, security, and documentation risks.

If a customer, auditor, or regulator asked you to show them a complete history of changes to an important record (pricing, contract terms, inventory adjustments), could you?

No. We have no audit trail. Changes are made and the previous version is lost.Maybe, with a lot of digging. Some systems keep logs, but they're hard to find or incomplete.For some systems, yes. For others, it would be difficult or impossible.Yes. Our critical systems maintain full audit trails with who changed what, when, and why.

Where does your most sensitive business data live (financial records, customer information, employee data, contracts)?

Spreadsheets on local computers, email attachments, and shared folders with no access controls.Mostly in cloud apps and shared drives, but access permissions haven't been reviewed in a long time.In dedicated systems with some access controls, but we're not confident about who has access to what.In secure, access-controlled systems with defined data ownership, retention policies, and regular access reviews.

How do you ensure that regulatory requirements, certifications, or contractual obligations are being met on an ongoing basis?

We react when something comes up. There's no proactive tracking of compliance requirements.One person keeps track of what's needed, mostly in their head or a personal spreadsheet.We have checklists and calendars for major compliance dates, but verifying we're actually compliant requires manual review.Compliance requirements are tracked in a system with automated reminders, evidence collection, and reporting.

What would happen if a critical business document (contract, insurance certificate, SOW, license agreement) needed to be found urgently?

It would take hours or days to find it. It might be in someone's email, a filing cabinet, or a random shared folder.We could probably find it, but it would require asking around and searching through multiple locations.Important documents are in a shared drive or document system, but there's no consistent naming or organization.Documents are in a managed repository with tagging, search, version control, and defined retention.

Back Next

Tool Sprawl & Technical Debt

These questions look at the state of your technology stack and whether your tools are helping or hindering you.

How many different software tools and applications does your organization use for day-to-day operations?

We have no idea. If we tried to count, we'd probably be shocked.A lot -- probably 15-25+. Many overlap and we're not sure which teams use what.We have a general sense -- maybe 10-15 -- and there's some overlap, but each serves a purpose.We maintain a documented inventory. Each tool has a defined purpose, an owner, and we regularly evaluate whether we still need it.

How would you describe the state of any custom-built tools, spreadsheets, or workarounds your team relies on?

There's a critical spreadsheet (or Access database, or custom script) that one person built years ago, and it runs a key part of our business. Nobody else understands it.We have several homegrown tools and complex spreadsheets. They work, but they're fragile and break when anything changes.Some custom tools exist and we know they need to be replaced, but they work for now and there are bigger priorities.We've systematically replaced or upgraded our custom workarounds. What remains is documented and maintainable.

When was the last time you evaluated whether your current tools and systems are still the right fit for your business?

We haven't. Most of our tools were picked years ago and nobody has questioned them since.Individual tools get evaluated when they break or when the contract comes up, but there's no holistic review.We review periodically, but usually only when there's a pain point. We don't proactively optimize.Annually. We review our full technology stack against business needs, cost, and integration capabilities.

How much do you spend on software subscriptions and tools that you suspect aren't being fully utilized?

We have no idea what we spend on software or how much is actually used.We're probably paying for several tools that nobody uses, or that only one person uses. We just never got around to canceling them.We know there's some waste, but it's not a big enough line item to prioritize fixing.We track software spend and utilization. Unused or redundant tools are identified and eliminated regularly.

Back Next

Almost Done -- Where Should We Send Your Results?

We'll generate a detailed scorecard with your Red/Yellow/Green grades across all 8 dimensions, plus specific recommendations for improvement.

Your Name

Email Address

Company

Phone (optional)

Your information is kept confidential and will only be used to deliver your assessment results.

Back See My Results

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Ep

28

Is Your Business Running on Duct Tape and Spreadsheets?

The Hidden Cost of Outgrown Operations

What You'll Get

About Your Business

Manual Processes & Human Error

Tribal Knowledge & Key-Person Risk

Data Silos & Disconnected Systems

Reporting & Visibility

Customer Experience & Response Time

Scaling & Growth Bottlenecks

Compliance & Risk

Tool Sprawl & Technical Debt

Almost Done -- Where Should We Send Your Results?