Development Agency
Contact Sign in Get a project quote

Service

Content portal development

For marketing leads and content directors running a multi-author blog, knowledge base or content brand that has outgrown a single-author blogging tool and needs approval, hubs, gating and measurement built in.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A content operation that started as one person writing a weekly post now has eight guest authors, a freelance editor and a marketing manager who is accountable for leads.

  • The blogging tool still assumes one author who publishes their own work.
  • Drafts arrive as email attachments and shared documents, the editor pastes them in by hand, and nobody can see which pieces are waiting for review and which are stuck with the author.
  • A guest author with publishing rights pushes a half-edited post live on a Friday evening.

Where it gets harder

The content itself has no structure.

  • Two hundred posts sit in a reverse-chronological list with a tag cloud; the pillar guide that should anchor a topic is buried under newer, weaker pieces.
  • The report that should capture leads is a PDF link on a page with no form, so downloads are counted but nobody is captured.
  • The monthly digest is assembled by copying links into an email tool.
  • When the marketing manager is asked which content brought in enquiries, the answer is a guess from three different dashboards.

Scope of the service

What the build covers

A custom content portal build normally covers the editorial chain from submission to measurement. Multi-author submission gives guest authors a workspace to draft and file; editorial approval moves each post through submitted, in review, approved and published, with the editor able to send it back with notes. Content hubs and pillar pages give each topic a home that collects its posts, guides and downloads in a deliberate order rather than by date. Reading time and a generated table of contents make long guides usable. Gated downloads put a form in front of a guide or report and record the lead with the asset and the page it came from. Topic subscriptions and digest emails let readers follow a hub and receive a periodic round-up assembled from what was published.

A content performance dashboard shows views, reads and conversions per post, hub and author, so the marketing manager can answer the question of what worked. The shared publishing layer provides revisions, scheduled publishing, categories and tags, media processing, feeds, caching and old-URL migration. Editions and ad server integration are left out by default, because content brands rarely need them, and added only when asked.

Deliberately out of scope

  • The CRM itself, which receives leads through an integration rather than being replaced
  • Marketing automation sequences, which stay in your email platform
  • Paid media management

When the scope grows

Scoping scenario

A professional-services brand with three practice areas wants a hub per practice, partner-authored posts that must pass a compliance review as well as an editorial one, gated reports feeding its CRM with the practice area attached, and a quarterly digest per hub. That two-stage approval is the kind of thing that makes a custom build the honest route, and the scope document names it.

Deliverables

What you receive

  • Discovery notes from mapping how posts currently move from author to live
  • A written scope document naming each approval stage, the hubs and what is left out
  • Designs of the hub page, the long guide template and the author workspace
  • The build, including gating, digests and the performance dashboard where in scope, deployed to your hosting or ours
  • Migration of existing posts, authors and tags with a redirect map
  • Training for editors, the marketing manager and a guest author session
  • Handover material and full ownership of the source code and your content

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 to the current blog, email platform, CRM and analytics; a list of authors and the hubs you expect to need.

    Project stage: Onboarding

  2. Planning

    Discovery with the content lead and the marketing manager; approval stages, hubs, gating and digest cadence are written into the scope document.

    Project stage: Planning

  3. Design

    Hub, guide and post templates designed for reading on a phone, with the gating form and table of contents in place.

    Project stage: Design

  4. Development

    Built in layers: authors and approval, then hubs and templates, then gating and lead capture, then digests and the dashboard.

    Project stage: Development

  5. Client review

    Your editors and two guest authors run a fortnight of real submissions and tell us where the flow does not match how you work.

    Project stage: Client review

  6. Revisions

    Changes from the review are made and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Posts migrated, redirects tested, the CRM connection verified with test leads, launch checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The team publishes through the new portal; hosting and maintenance continue under their own agreement if taken.

    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.

  • CRM systems for captured leads with source and asset attached
  • Email and newsletter platforms for digests and topic subscriptions
  • Analytics and consent management platforms
  • Marketing automation tools for follow-up sequences
  • Document storage for the source files behind gated downloads
  • Social publishing tools for distribution

How we would approach it

Worked example

Concept demo

A professional-services brand with two-stage approval

The situation

A professional-services firm wants partners in three practice areas to write for the site, but every post must pass both an editorial review and a compliance review before it can go live, and gated reports must reach the CRM tagged with the practice area that produced them.

Why it is a custom build

The custom route is needed because of the two-stage sign-off with an audit record, which goes beyond the single editorial approval the package assumes.

The scope we would propose

  • A hub per practice area
  • An approval chain with two distinct reviewer roles and a visible record of who signed off, gated downloads whose lead record carries the hub and the asset
  • A quarterly digest assembled per hub from what was published

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 authors and whether guest authors need their own workspace
  • Number of approval stages and reviewer roles
  • Number of hubs and how much existing content needs reorganising into them
  • Gated downloads and the CRM the leads must reach
  • Digest cadence and the email platform to connect
  • Volume of posts, images and tags to migrate
  • Depth of the performance dashboard beyond views, reads and conversions
  • Hosting choice: your own hosting or ours

Start from a package

Content portal package

Multi-author submission with approval, content hubs, gated downloads, digest emails and a performance dashboard for content brands and knowledge publishers.

Custom build
View the package

FAQ

Frequently asked questions

When is the package enough and when do we need a custom build?

If one editorial approval stage, a set of hubs and standard gating cover your needs, the content portal package is the right fit and we quote for that. Multiple reviewer roles, unusual lead routing or a dashboard that needs data from outside the portal point to the custom route.

Can guest authors publish without an editor?

Only if you decide they can. Publishing rights are a permission, and the default is that every submission passes through an editor before it goes live. You choose per author.

Will captured leads reach our CRM?

Where your CRM has an interface we can connect to, yes: each lead is sent with the asset, hub and page it came from. The scope document states how the connection works once we have confirmed the CRM.

Can you move our existing posts into hubs?

Yes. Posts, authors, tags and images are migrated with a redirect map, and we agree a hub assignment for the existing content during planning so the archive is organised from the day you launch.

Who owns the portal afterwards?

You do. The source code, posts, leads and media are handed over at delivery. Hosting and maintenance are optional and agreed separately.

Get a project quote for blog and content portal 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