Skip to content
PapelSoftware

Business websites

A business website your team can keep up to date

We design and build company and marketing websites under a development plan, then hand them over on Papel Sites so your staff can edit pages, publish posts and manage forms without filing a ticket.

Who it's for

Clients usually come to us for business websites in one of these situations.

  • Your current site is hard to change

    Every new page or price update goes through a developer or a former agency, so marketing waits weeks for changes that should take an afternoon.

  • You're repositioning or entering new markets

    New services, a new audience or a second language need a site structure that holds up, not another set of pages bolted onto the old navigation.

  • Visitors arrive but don't get in touch

    Forms are buried, pages load slowly on phones and nobody can say which pages produce inquiries. The site needs clearer paths to contact and basic measurement.

What we build

A website is rarely finished at launch. We build it so the people who know your business can change it themselves, and keep our engineers for the work that needs code.

Corporate sites
Company, services, team and contact pages written for the buyers you sell to, with clear calls to action and fast load times.
Landing pages
Campaign and product pages built from reusable sections, so marketing can launch a new page in an afternoon.
Multi-language sites
Localized pages with proper hreflang tags, language switching and per-locale URLs, ready for translated content.
Blogs and resource centers
Articles, categories, authors and search, with structured data so posts appear correctly in search results.
Forms and lead capture
Contact, quote and demo request forms with spam protection, email notifications and handoff to your CRM.
Redesigns and migrations
Moving an older site to a modern build, with redirects mapped page by page so existing search rankings carry over.

How we approach it

Every request moves through the same steps, inside your weekly release cycle.

  1. 01

    Content and structure first

    We agree on pages, navigation and the message for each audience before visual design starts.

  2. 02

    Design a section library

    Instead of one-off pages, we design reusable sections that your team can combine into new pages later.

  3. 03

    Build on Papel Sites

    The site is built so every section is editable in the Papel Sites dashboard, with roles and approvals for your editors.

  4. 04

    Launch and train

    We handle domains, redirects and analytics at launch, then run a short training session for the people who will edit the site.

Typical timeline

Engagement timeline

A typical schedule for a first launch. Your plan's weekly releases continue after launch for new pages and changes.

About 10 weeks to launch

  1. Weeks 1 to 2

    Content plan and sitemap

    Audit of current pages, a sitemap, and the message and call to action for each audience.

  2. Weeks 2 to 4

    Section library design

    Reusable sections designed in Figma and approved on real content, not placeholder text.

  3. Weeks 4 to 8

    Build on Papel Sites

    Sections built as editable components, with forms, analytics and the redirect map.

  4. Weeks 7 to 9

    Content entry and checks

    Pages filled in, accessibility and performance checks run, and redirects tested against old URLs.

  5. Weeks 9 to 10

    Launch and training

    DNS cutover, sitemap submitted, and a training session for the people who will edit the site.

Typical for a business site of 10 to 20 pages on a Starter plan. Whether your copy is ready is the biggest variable; we'll give you a schedule for your scope after the first call.

What you get every week

Releases happen on a fixed day each week. Monday starts with a queue check; Friday ends with these in your inbox and your shared channel.

  • Pages you can click

    Every page in progress has a private preview link, so you review the real thing on your own phone and laptop instead of a static mockup.

  • Friday release

    Approved pages and changes go live on release day, with written notes listing what changed and which URLs were affected.

  • A short demo video

    A few minutes walking through the week's work, useful for sharing with colleagues who weren't on the thread.

  • Next week's plan

    What we'll work on next and anything we need from you, such as copy, photos or a decision on a section.

Quality standards

The targets we hold this work to, and how we check them. These are our commitments for how the work is done, not certifications.

Accessibility
Our targetWCAG 2.2 Level AA as the target for every template and section.
How we checkAutomated axe checks on each pull request, plus a manual keyboard and screen reader pass on key templates before launch.
Core Web Vitals
Our targetThe "good" range at the 75th percentile: LCP 2.5 seconds or less, INP 200 ms or less, CLS 0.1 or less.
How we checkLighthouse budgets run on preview builds; field data from Google Search Console reviewed after launch.
SEO basics
Our targetUnique titles and descriptions, canonical URLs, an XML sitemap, structured data where it applies, and a permanent redirect for every retired URL.
How we checkA crawl of the staging site before launch and a redirect test run against the old site's URL list.
Images and media
Our targetResponsive image sizes, modern formats and lazy loading below the fold.
How we checkHandled by the build pipeline and confirmed in code review.
Forms
Our targetSpam protection, server-side validation and confirmed delivery to every recipient.
How we checkA test submission to each notification address and CRM connection before launch.
Third-party scripts
Our targetNo tracking or chat scripts added without your approval, and a cookie banner where your analytics setup needs one.
How we checkA script inventory reviewed with you at launch.

After launch, your team runs the site

Papel Sites, our website management product in early access, is where clients manage their site once it's live. Our engineers stay available through your plan for anything that needs code.

Edit pages and sections

Change text, images and calls to action, or build a new page from the section library, with a preview before publishing.

Publish the blog

Write, schedule and publish posts with categories and authors. Version history lets you roll back any change.

Manage forms and SEO

See form submissions, set notification recipients, and edit page titles, descriptions and social images.

Draft with Claude

A writing assistant built on Anthropic's Claude helps draft pages, tighten copy, suggest SEO titles and prepare translations. Your editors review everything before it goes live.

Typical deliverables

What you can expect to have in hand, in accounts and repositories you own.

  • Designed and built website on your own domain
  • Reusable section library for new pages
  • Editor access in Papel Sites with roles for your team
  • SEO basics: metadata, sitemap, structured data and redirects
  • Accessibility checks against WCAG 2.2 AA
  • Short training session and written editor guide

Illustrative example, not a client case study

Example engagement

A professional services firm replaces an agency-built site

Picture a mid-sized consulting firm whose website was built years ago by an agency that has since moved on. Service pages are out of date, the team can't edit them, and the contact form sends leads to a former employee's inbox.

  1. Weeks 1 to 2

    Decide what stays

    We list every existing page with its search traffic, then agree which pages to keep, merge or retire, and write a sitemap around the firm's three main services.

  2. Weeks 2 to 4

    Design a section library

    Hero, service summary, team, insight list and contact sections are designed once, using the firm's real copy, and approved by the managing partner.

  3. Weeks 4 to 8

    Build and map redirects

    Sections are built on Papel Sites. Every retired URL gets a permanent redirect, and the quote form sends leads to the firm's CRM and a shared inbox.

  4. Weeks 9 to 10

    Launch and hand over

    DNS moves on a quiet morning, the sitemap is submitted, and the marketing lead and two partners get an hour of editor training.

Where it ends up

The firm's marketing lead now publishes service pages and articles from the Papel Sites dashboard, leads reach the right people, and the development plan can be paused until the next project.

Technologies we use

A short, well-known list. We'd rather know a few tools deeply than list every framework we've touched.

Technologies used for business websites
AreaTools
BuildNext.js, TypeScript, Tailwind CSS
EditingPapel Sites, Claude writing assistant
IntegrationsHubSpot, Salesforce, Google Analytics, Plausible

Which development plan fits

Business websites is delivered under a development subscription. These are the plans that suit this work best.

  • Starter

    $390 per month, best fit

    One active request at a time is usually enough to design, build and launch a business website.

    Start with Starter
  • Growth

    $790 per month

    Website and web or mobile app in parallel, with a dedicated designer and a shared design system.

    Start with Growth

After launch, you can end the development plan and keep the site on a Papel Sites plan, then start a plan again when you need new work. About Papel Sites

Compare all development plans

Common questions

If yours isn't here, ask us on a call or by email.

Can we edit the site ourselves after launch?

Yes. That's the point of building on Papel Sites. Your team edits pages, posts, forms and SEO settings from a dashboard. Changes that need new code, such as a new section type or integration, go into your development queue.

Do we have to keep a development plan after launch?

No. Once the site is live, you can cancel your development plan at the end of a billing period and keep the site running on Papel Sites. You can subscribe again whenever you need new work.

Will we lose search rankings when we move from our old site?

We map every old URL to its new page with permanent redirects, keep metadata where it's working and submit the new sitemap. Rankings can shift during any migration, but these steps keep the risk low.

Does the Claude writing assistant publish content on its own?

No. It produces drafts and suggestions inside the editor. A person on your team reviews and publishes every change.

Who writes the content?

You know your business best, so the facts come from you. We provide page outlines, edit for clarity and length, and set up the Claude writing assistant for drafts. If you'd like us to write pages from interviews with your team, that work goes into your queue like any other request.

Can you build on another CMS, such as WordPress?

We build business websites on Papel Sites by default because it keeps editing simple and hosting managed. If you're committed to another CMS, tell us on the first call and we'll say plainly whether we can do it well under a development plan.

Talk to an engineer about business websites.

A 30-minute call with an engineer, not a sales script. You'll leave with a scope, a plan recommendation and a start date.