B2B Client case study · HR technology

From idea to 11K monthly visitors for a new HR management SaaS

A startup came to us with an idea, a founding team and nothing else. No product, no brand and no website. We built all three, then brought in customers through SEO, social media and Google Ads.

~11K organic visits per month
3 growth channels working together
7 services from one partner
11 specialists on the team

At a glance

The project in one minute

Client
A startup building HR management software for small and mid-sized businesses
Sector
HR technology, B2B SaaS
Starting point
An idea, a founding team, and no product, brand or website
Team
11 specialists
Build
Discovery to launch, then an ongoing monthly marketing retainer
Main growth channel
Organic search
What we delivered
Headline result
About 11,000 organic visits per month and a steady flow of qualified leads

Overview

A problem the founders knew well

Small and growing companies were running HR on spreadsheets, shared folders and chat messages. Leave requests, employee records, onboarding steps and performance reviews were scattered everywhere.

The founders wanted a simple, affordable HR platform that any team could start using in a day. They came to us with the idea and little else.

We became their single partner for everything that followed. We shaped the look and voice of the brand, designed and built the product, launched a marketing website, and then brought in customers through search, social media and paid ads.

Where HR lived before

SpreadsheetsShared foldersChat messages

One simple HR platform

Today the product has a recognizable brand, a fast website that ranks for the terms HR buyers search for, and a pipeline of leads that grows every month.

The challenges

Starting from zero in a crowded market

Each of these can slow a new SaaS launch. This team faced all six at once.

No brand to stand on

The company had no logo, no tagline and no visual identity.

Why it mattered In a crowded HR software market, a product without a clear identity looks like every other tool, and buyers hesitate to trust it.

A product that had to be simple

HR software has a reputation for being heavy and confusing. The founders wanted something a non-technical office manager could set up without training, with enough depth to grow with a company.

Why it mattered Simple and capable pull in different directions. Getting both right needed careful design.

A crowded, competitive market

HR and people management tools are one of the most competitive SaaS categories. Large, established players dominate the obvious search terms and advertising space.

Why it mattered Competing head on for the biggest terms would be slow and expensive for a new brand.

No audience and no traffic

The domain was brand new, with no content, no backlinks and no following.

Why it mattered The company needed customers, but nobody knew it existed.

Limited budget, long sales cycles

As a startup, the founders could not afford channels that did not convert. HR buyers also take time to decide.

Why it mattered Marketing had to build trust over weeks, not just chase quick clicks.

Too many moving parts for one small team

Branding, product, website and marketing usually mean four different vendors and four different messages.

Why it mattered The founders wanted one consistent story across everything.

Project goals

What the founders needed

Each goal answers one of the challenges, and each one maps to something we built.

  1. Before

    No logo, tagline or identity

    A brand people can trust

    Logo, tagline, color palette, typography and a brand voice guide

  2. Before

    HR software seen as heavy and confusing

    A product anyone can set up

    Flows designed around three user types and tested as prototypes before code

  3. Before

    Big players own the obvious terms

    A clear place in the market

    Positioning built on simplicity for smaller teams that enterprise tools underserve

  4. Before

    A new domain with no traffic

    A steady source of new prospects

    An SEO strategy in six layers, from keyword research to authority building

  5. Before

    Little budget and slow buyers

    Leads now while trust builds

    Google Ads on high-intent terms and LinkedIn content that builds familiarity

  6. Before

    Four vendors, four messages

    One consistent story

    Brand, product, website and marketing from one team

Timeline and team

From discovery to launch, then growth every month

Discovery and brand came first, because the positioning shaped every later decision. The marketing website was built in parallel. After launch, SEO, social media and Google Ads continued on a monthly retainer.

Project phases and their lengths
  1. Discovery and positioning3 weeks
  2. Brand identity4 weeks
  3. Product design6 weeks
  4. Product development5 months
  5. Testing and launch1 month
  6. Website design and development6 weeks, in parallel
  7. SEO, social media and Google AdsOngoing monthly retainer

The project team

Project team by role
RolePeople
Project manager 1
Brand and UI/UX designers 2
Frontend developers 2
Backend developers 3
QA engineer 1
SEO specialist 1
Social media and paid ads specialist 1
Total 11

Why the team looked like this

  • Brand and UI/UX designers together meant the identity and the product were designed as one.
  • Three backend and two frontend developers covered a platform with records, workflows, roles, reports and notifications.
  • An SEO specialist and a paid and social specialist joined the same team, so growth was planned alongside the build.
  • A project manager and a QA engineer kept one plan and one quality bar across every part.

How we delivered it

Eight steps from idea to growth

Four steps built the company. Four steps brought in customers. Here is what happened in each, what it produced and why it mattered.

  1. Discovery and positioning 3 weeks

    We interviewed the founders, studied the target buyers, HR managers, office managers and business owners, and mapped competitors to find gaps.

    What we found

    The clearest opening was simplicity. Most tools were built for large enterprises, leaving smaller teams underserved.

    Why it mattered

    This insight became the brand positioning and shaped every decision that followed.

  2. Brand identity 4 weeks

    We created the brand from the ground up.

    What it produced

    A clean, approachable logo that works at any size, from a browser tab to a pitch deck. A tagline that explains the promise in plain language. A calm, trustworthy palette with strong contrast and readable fonts. A brand voice guide for the website, emails, social posts and in-app text.

    Why it mattered

    A new product needs to look credible before buyers will try it. A shared voice guide keeps every channel sounding like one company.

  3. Product design (UX/UI) 6 weeks

    We designed around three kinds of users, HR admins, managers and employees. We mapped their daily tasks, sketched the core flows and tested clickable prototypes before any code was written.

    What it produced

    Requesting leave, approving it and updating a record each take only a few clicks. A new company can finish setup quickly without a manual.

    Why it mattered

    Testing prototypes is far cheaper than changing finished code. It kept the product simple, which was the whole positioning.

  4. SaaS development 5 months

    Our team built the platform with a modular architecture, so features could be added without rewriting the foundation.

    What it produced

    Employee profiles and records. Leave and time off with approval workflows. Attendance tracking. Onboarding checklists. Document storage and sharing. Role-based access and secure login. Reports and dashboards. Notifications and email reminders.

    Why it mattered

    We launched with this focused set, then kept adding features based on real customer feedback.

  5. Website design and development 6 weeks, in parallel

    We designed and built the marketing website with one job. Turn visitors into trials and demo requests.

    What it produced

    A clear homepage. Pages for each feature, plus pricing and demo booking. Fast, mobile-friendly pages. Clear calls to action and simple forms. Analytics and conversion tracking from day one.

    Why it mattered

    Because the same team handled brand, product and website, the site feels like a natural extension of the software.

  6. SEO, the long-term growth engine Ongoing

    SEO became the company’s most valuable channel. We built the strategy in six layers, explained in the next section.

    What it produced

    Keyword research, a technical foundation, feature and solution pages, a content library, authority building and monthly optimization.

    Why it mattered

    Search keeps bringing in prospects without paying for every click.

  7. Social media marketing Ongoing

    We set up and managed the company’s social presence, mainly on LinkedIn, where HR and business decision-makers spend their time.

    What it produced

    Consistent posts on HR best practices, product updates and team culture. Short educational content. Founder-led posts that gave the brand a human face. Retargeting audiences from social and website visitors.

    Why it mattered

    Social built familiarity, so prospects already recognized the brand when they later saw it in search or ads.

  8. Google Ads Ongoing

    While SEO built momentum, Google Ads delivered leads from the start.

    What it produced

    Campaigns on high-intent search terms. A dedicated landing page for each campaign. Keyword and negative keyword management. Conversion tracking tied to trials and demos. Ongoing testing of copy, audiences and pages to lower the cost per lead.

    Why it mattered

    Ads showed which messages and keywords converted best, and those insights improved the SEO content.

SEO deep dive

Inside the SEO strategy

A brand new domain cannot win the biggest HR terms straight away. The strategy was built in layers, so each one made the next more effective.

  1. Keyword research

    We identified what HR buyers actually search for, from problem terms to buying terms.

  2. Technical foundation

    Clean site structure, fast load times, correct indexing, schema markup and mobile optimization.

  3. Feature and solution pages

    Pages for high-intent searches, each answering one buyer question and leading to a demo.

  4. Content strategy

    Guides, templates, checklists and comparison articles that reach HR professionals early in their research.

  5. Authority building

    Quality backlinks and digital PR to build the domain's credibility in a competitive space.

  6. Ongoing optimization

    Monthly reviews of rankings, traffic and conversions to refine pages and double down on what works.

Two kinds of search, two kinds of page

Search intent and page types
Problem searchesBuying searches
Example from this project“how to track employee leave”“HR software for small business”
Who is searchingHR professionals early in their researchBuyers ready to compare tools
Page that answers itGuides, templates, checklists and comparison articlesFeature and solution pages
Next step offeredLearn more and get to know the brandBook a demo or start a trial

Google explains the basics of how search works in its SEO Starter Guide (opens in a new tab), and how schema markup helps it understand a page in its introduction to structured data (opens in a new tab).

Growth system

How the channels work together

SEO, social media and Google Ads were not run as separate projects. Each one made the others work better.

Social builds recognition

Founder-led, educational posts meant prospects already knew the brand when they met it in search or ads.

Ads bring early leads

High-intent campaigns delivered leads while organic rankings were still growing.

SEO compounds over time

Content keeps working long after it is published, without paying for every visit.

Key decisions

The choices that shaped the project, and why

Key project decisions and the reasoning behind them
DecisionWhy it made sense
Find the market gap before designing anything Positioning on simplicity for smaller teams gave the brand, product and marketing one clear direction.
Design for three user types HR admins, managers and employees need different things. Designing for each keeps every screen focused.
Test clickable prototypes before writing code Problems found in a prototype cost far less to fix than problems found in finished software.
Build a modular architecture New features can be added without rewriting the foundation, which suits a product shaped by customer feedback.
Launch with a focused feature set The essentials went live first. Later features came from what real customers asked for.
Build SEO into the website from day one Structure, speed and indexing are easier to get right at the start than to fix later.
Focus social media on LinkedIn That is where HR and business decision-makers spend their time.
Run Google Ads while SEO grows Search rankings take time. Ads brought leads in the meantime and showed which messages converted.

The product

Inside the HR platform

The first release covered the essentials a small HR team needs every week. New features have been added since, based on customer feedback.

A leave request in a few clicks
  1. Employee requests leaveFrom their own view of the platform
  2. Manager approves itNotified by email and in-app
  3. Records updateLeave balances and calendars

Central employee records

One secure place for profiles, contracts and documents.

Leave and time off

Requests, approvals, balances and calendars.

Attendance tracking

Simple check-in tools with clear summaries.

Onboarding workflows

Checklists and tasks that help new hires get started smoothly.

Role-based access

Admins, managers and employees each see only what they should.

Reports and dashboards

Live visibility into headcount, leave and attendance.

Notifications

Automatic reminders and approvals by email and in-app.

Three users, one system

HR admins

Set up the company, manage records, run onboarding and see reports.

Managers

Approve requests and see what their team needs.

Employees

Request leave, check in and find their own documents.

Tech stack

The technology behind the product and the growth

A simplified view of how the product fits together, then what each tool does. The names link to official documentation.

HR adminsManagersEmployees
Web appReact · Next.js · TypeScript
Application servicesNode.js
DatabasePostgreSQL
In-memory storeRedis

Runs on AWS

DockerCI/CD pipeline

Front end

Back end and data

Infrastructure

Growth tools

Results

What the company has now

~11,000organic visits per month

From a domain that started with no content, no backlinks and no following.

  • Qualified leadsA steady, growing flow of demo requests and trial signups
  • Paid leads from the startHigh-intent leads from Google Ads while rankings grew
  • A live productA working HR platform that keeps shipping features
Results by area
AreaOutcome
Organic traffic About 11,000 visits per month from search, built from a brand new domain
Lead generation A steady, growing flow of qualified demo requests and trial signups through SEO
Paid acquisition Google Ads delivering high-intent leads while organic rankings grew
Brand presence Consistent identity across product, website, search and social media
Product A live, working HR platform that continues to ship new features
Marketing channels SEO, social media and paid ads working together as one system

Most importantly, the company now owns an acquisition channel that does not depend on advertising spend alone. Organic search brings in new prospects every day, and the content library keeps working long after it is published.

Why it worked

Five reasons the project worked

One team, one story

Brand, product, website and marketing came from the same partner, so every touchpoint felt consistent.

Positioning before pixels

We found a clear gap in the market before designing anything.

SEO from day one

The website was built with search in mind, not retrofitted later.

Paid and organic together

Ads delivered early leads and taught us what to rank for.

Continuous improvement

We kept testing, measuring and refining after launch.

Takeaways

Lessons for SaaS founders

What other founders can take from this project, especially if they are launching into a crowded category.

Questions to answer before you build

  • Which buyers do the big players serve poorly?
  • What does your product promise, in one plain sentence?
  • Who are the different users, and what does each one do every day?
  • Which features are essential for the first release?
  • How will people find you while your domain is new?

What this project shows

  1. Positioning comes first. One clear gap, simplicity for smaller teams, guided the brand, product and marketing.
  2. Test before you code. Clickable prototypes kept the product simple before development began.
  3. Launch focused, then listen. A small set of essentials went live first, and customer feedback shaped what came next.
  4. Start SEO with the website. Organic search became the most valuable channel because it was planned from day one.
  5. Use ads to learn, not only to sell. Paid search brought early leads and showed which keywords to target with content.

Planning your own build? Our free SaaS MVP cost calculator helps you estimate scope, team and timeline.

FAQs

Questions about this project

How did a new domain reach about 11,000 organic visits a month?

Through SEO built in layers. Keyword research, a clean technical foundation, feature and solution pages for buying searches, helpful content for early research, authority building and monthly optimization.

What services were included?

Brand identity, product UX/UI design, SaaS development, marketing website design and development, SEO, social media marketing and Google Ads, all from one team.

How long did the build take?

Three weeks of discovery and positioning, four weeks of brand identity, six weeks of product design, five months of development and one month of testing and launch. The website took six weeks in parallel. Marketing continues on a monthly retainer.

What technology was used?

React, Next.js and TypeScript on the front end. Node.js, PostgreSQL and Redis on the back end. AWS, Docker and a CI/CD pipeline for infrastructure. Google Analytics, Google Search Console and Google Ads for growth.

Why use Google Ads if SEO worked so well?

SEO takes time to build. Ads brought high-intent leads from the start and showed which messages and keywords converted, which improved the SEO content.

Which social channel did you focus on?

Mainly LinkedIn, because that is where HR and business decision-makers spend their time.