How to Recommend the Right Website or App for Your Client

A guide for Sales, Account Managers, and Project Managers

1. Start with Goals, Not Technology

When a client approaches us, our first instinct should not be to think about which technology to use. Instead, we need to understand what problem they are trying to solve or what goal they want to achieve.

The wrong approach: “They need a website, so let’s build them a WordPress site.”

The right approach: “What are they trying to accomplish? What problems are they facing?”

This single shift in thinking will help you recommend the right solution and set proper expectations from the start.

2. The Framework: Nine Purpose Categories

Every client request falls into one of these nine categories. Understanding which category fits their need is the first step to making the right recommendation.

| Purpose | Typical Solutions | Examples |

|---------|-------------------|----------|

| Marketing & Brand Presence | CMS website or static website | Company website, portfolio, landing pages. Think SpaceX or Tesla. |

| Selling Products Online | E-commerce solutions | Online store, product catalog with cart. Think Amazon or Shopify stores. |

| Listing & Directory | Classified listing or marketplace website | Job board, property listings, service marketplace. Think Craigslist, Indeed, or Zillow. |

| Service Booking | Booking and reservation systems | Restaurant ordering, hotel reservations, appointment scheduling. Think Marriott, Starbucks, or KFC. |

| Internal Business Tools | Custom applications | Document management, incident tracking, file sharing. These are internal systems not visible to the public. |

| Customer Self-Service | Customer-facing applications | Queue management, loyalty points app. Think bank apps or airline check-in portals. |

| Lead Generation | CRM applications | Sales pipeline, contact management, lead tracking. Think HubSpot or Salesforce. |

| School & Education | School management and LMS solutions | Student portals, course management, attendance. Think Harvard, Oxford, Udemy, or Coursera. |

| Enterprise Operations | ERP systems | Inventory, accounting, HR, procurement. Think SAP or Oracle ERP. |

3. Decision Factors

Once you identify the purpose category, the specific solution depends on several factors:

Requirements

What features does the client actually need? A simple brochure site requires different technology than a site with user accounts, payments, or real-time updates.

Timeline

How soon do they need it? A tight deadline may push toward off-the-shelf solutions rather than custom development.

Budget

What can they afford? This affects whether we recommend a template-based CMS, a customized platform, or a fully custom build.

Technical Experience

Who will manage it after launch? If the client has no technical staff, we need to recommend solutions with user-friendly admin interfaces.

Resources

Do they have content ready? Do they have staff to maintain it? A content-heavy site is useless if no one will update it.

4. When to Recommend Complex Solutions

Two factors consistently push projects toward more complex (and expensive) solutions:

Integration Requirements

When the client needs the website or app to connect with other systems, complexity increases significantly. Examples include syncing with accounting software, pulling data from external APIs, connecting to payment gateways, or integrating with inventory systems.

Custom Workflows

When the client has specific business processes that must be replicated in the system, off-the-shelf solutions rarely fit. Examples include multi-level approval processes, custom pricing rules, unique order fulfillment flows, or industry-specific compliance requirements.

If you hear either of these in client conversations, flag it early. These requirements significantly affect scope, timeline, and budget.

5. Common Pitfall: The Client Who Doesn’t Know What They Need

This happens frequently with clients planning their first online business. They come with vague ideas and feature requests that don’t match their actual goals.

The Classic Example

A client says they want a “directory listing website” but then starts asking for features like user profiles, messaging between users, activity feeds, and friend connections. What they’re actually describing is a social network, not a directory.

How to Handle This

1. Listen to the features they request, but focus on the problem they’re trying to solve.

2. Ask clarifying questions: “What will your users primarily come to this site to do?”

3. Help them understand the difference between what they asked for and what they actually need.

4. If their vision is too ambitious for their budget or timeline, help them prioritize.

This is a consultative skill that builds trust. Clients appreciate when we help them avoid costly mistakes.

6. Key Takeaway

Before any discussion about technology, platforms, or features, always start with one question:

“What problem are you trying to solve, or what goal are you trying to achieve?”

The answer to this question determines everything else. Master this, and you will consistently recommend the right solutions for your clients.