Development Agency
Contact Sign in Get a project quote

Service

Business directory development

For directory operators and niche publishers who list local or sector businesses and need the category schema, area taxonomy, claim process, paid packages, imports and enquiry tracking designed around their own coverage rather than a generic listings theme.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

Most directories start as a spreadsheet exported into a listings theme, and the theme decides everything afterwards.

  • Every listing has the same six fields, so a restaurant and a roofing firm carry the same form and neither says anything useful; opening hours live in a free-text box that is never the same twice.
  • Areas are a flat tag list, so a business in a village appears under the village but not under the town or the county, and the person maintaining the site does not know which.
  • A business owner rings to say their phone number is wrong, the editor changes it by hand, and nobody records that the owner was the person who asked.

Where it gets harder

Paid listings are handled by invoice and memory: a featured slot is sold, the editor ticks a box, and six months later it is still featured because nobody noted when it was due to end.

  • A second import from a data supplier doubles half the listings because the names differ by a suffix.
  • Enquiries sent through the contact form go to the editor's inbox and are forwarded on, so the operator cannot tell a business how many leads its listing produced, which is the one number that would sell the upgrade.
  • The directory looks full but the operator cannot say how many listings are claimed, current or paying.

Scope of the service

What the build covers

A custom business directory build normally covers:

  • A listing schema per category So each category carries its own attribute set and its own validation
  • An area taxonomy with nested levels (region Town, district) and a map search driven from geocoded addresses
  • A claim process Where the person claiming receives a code through a channel already on the listing, such as the listed phone number, an email address at the listed domain, or a letter to the listed address, and the claim is recorded with the channel used and the date
  • Owner self-service edits That go through a moderation queue before they show
  • Listing packages and featured placement with a start and end date A visible label on every featured listing and the tier rules published on a page visitors can read
  • Bulk import with deduplication rules An update queue for records that changed in the source and data-quality flags for missing fields
  • Enquiry forwarding with a per-listing count the owner can see
  • Category landing pages With an editorial introduction written per category rather than generated

How discovery works

Discovery follows one listing from import to its first enquiry with you: where the starting data comes from and how often it changes, which categories need which fields, how areas nest, what a claimant must prove and through which channel, what each paid tier includes and how it is labelled, who moderates edits and reviews, and what an owner should see about their own listing. Each answer becomes a named stage in the scope document: import, deduplicate, publish, claim, enrich, moderate, feature, enquire, report.

Deliberately out of scope

  • Taking bookings or payments between visitor and business, the business's own website, and any promise about where directory pages appear in search engines. We build crawlable category and area pages with structured listing data and sensible metadata
  • What a search engine does with them is outside anyone's control

When the scope grows

Scoping scenario

A county-wide directory with forty categories, a three-level area tree, a starting dataset from two suppliers that overlap, and a paid tier that sells a featured position on category and area pages. That is a different build from a single-town directory maintained by hand, and the scope document says which is being built.

Deliverables

What you receive

  • Discovery notes from following one listing from import to first enquiry
  • A written scope document naming each stage from import to reporting, with what is out of scope
  • Design of the category page, the listing page, the claim flow, the owner dashboard and the moderation queue, on mobile for visitors and owners and desktop for the editorial team
  • The build, deployed to your hosting or ours
  • Import of your starting dataset with deduplication rules agreed and a report of what was merged, flagged or rejected
  • Training for editors and moderators, with a short written guide for claims and featured placement
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts, your category list, area list, starting dataset samples and the paid tiers you sell today.

    Project stage: Onboarding

  2. Planning

    Discovery with the operator, an editor and whoever sells packages; the scope document, the claim rules and the milestone plan are agreed.

    Project stage: Planning

  3. Design

    Clickable designs of a category page, a listing page, the claim flow and the owner dashboard, reviewed with two business owners you know.

    Project stage: Design

  4. Development

    Built in stages: schema, areas and import first, then claims and owner edits with moderation, then packages and featured placement, then enquiries and reporting.

    Project stage: Development

  5. Client review

    Your editors run a test import, claim listings through each channel, moderate real edits and sell a test package end to end.

    Project stage: Client review

  6. Revisions

    Category fields, deduplication thresholds, claim wording and tier labels are adjusted from the review and re-checked against the scope.

    Project stage: Revisions

  7. Ready for launch

    Full dataset imported, redirects from old listing URLs mapped, enquiry forwarding tested to addresses you control, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The directory runs on the new platform; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Geocoding and mapping services for addresses, area boundaries and map search
  • Card payment providers for listing packages and featured placement
  • Email and SMS providers for claim codes, enquiry forwarding and renewal notices
  • Data suppliers delivering listing feeds by file or API
  • Accounting software for package invoices and renewals
  • Email marketing platforms for owner newsletters and renewal campaigns
  • Image storage and optimisation services for listing photographs

How we would approach it

Worked example

Concept demo

A county directory merging two supplier datasets

The situation

A county directory operator held one dataset bought from a business data supplier and another collected by hand over several years, with roughly a third of the records describing the same businesses under slightly different names.

Why it is a custom build

This needs a custom build because the merge rules and the review queue are specific to the two datasets, and because the featured-placement rule has to be enforced by the page rather than by an editor remembering it.

The scope we would propose

  • A deduplication pass on import that matches on normalised name, postcode and phone number, merges with a preference order per field, and sends uncertain matches to a review queue rather than guessing
  • A three-level area tree populated from geocoded addresses so each listing appears in its district, town and region
  • A claim flow offering a call to the listed number, an email to the listed domain or a posted letter
  • A featured tier with a published rule that at most three featured listings appear at the top of any category or area page, each carrying a visible label

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of categories and how different their attribute schemas are
  • Depth of the area taxonomy and whether map search is needed
  • Size and quality of the starting dataset and the deduplication rules required
  • Claim channels supported: phone code, domain email, postal letter
  • Paid tiers, featured placement rules and the payment provider involved
  • Moderation workflow for owner edits and reviews
  • Enquiry forwarding and the owner statistics required
  • Redirect mapping from an existing directory
  • Hosting choice: your own hosting or ours

Start from a package

Business directory package

Category listing schemas, nested areas with map search, claim by code to the listed channel, owner edits through moderation, listing packages with labelled featured placement, imports with deduplication and enquiry counts per listing.

Custom build
View the package

FAQ

Frequently asked questions

Would the package do, or do we need a custom build?

An operator with a few dozen categories, a two-level area list, one starting dataset and a simple featured tier is usually covered by the business directory package through configuration. A custom build is the honest answer when several overlapping datasets must be merged, when the area model is unusual, or when packages are sold through a sales team with bespoke terms. Discovery is where we tell you which.

How does a business prove it owns a listing?

By receiving a code through a channel that is already on the listing: a call or text to the listed phone number, an email to an address at the listed domain, or a letter to the listed postal address. The platform records which channel was used and when. It does not inspect documents or vouch for the business; it records that someone with access to that channel claimed the listing.

Will the directory rank well in search engines?

We cannot promise that, and we do not. What we build is crawlable: one URL per listing, category and area, structured listing data, titles and descriptions generated from the schema, and a sitemap that updates when listings change. How any search engine treats those pages is outside our control and outside the scope document.

How is featured placement shown to visitors?

Every featured listing carries a visible label, the number of featured positions per page is fixed in configuration, and the tier rules are published on a page visitors can read. Featured placement never changes a rating or a review; it changes position and labelling only.

Who owns the directory afterwards?

You do. Source code and your data, including listings, claims, packages and enquiry history, are handed over at delivery; hosting and maintenance are optional and separately agreed.

Get a project quote for business directory software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences