Skip to content

Digital services for service businesses

One studio for the public website and the systems behind the work.

PlinthWeb can shape the website customers see, the custom application or automation the team uses, and the digital strategy that connects search, social content, paid campaigns, conversion, and measurement. Each engagement has a defined owner, operating boundary, and evidence-based next step.

Discuss a project

Your context travels with you. The form will keep this services page as the inquiry source.

  1. 01

    Custom websites and business applications built for real workflows

  2. 02

    Workflow automation, integrations, and dependable system handoffs

  3. 03

    Digital strategy, SEO, social media, and pay-per-click campaigns

  4. 04

    Responsive design, accessibility, security, analytics, and launch QA

  5. 05

    Managed hosting, reporting, and deliberate ongoing optimization

Service paths

Choose the scope that matches the problem.

01

Direct accountability

The person shaping the strategy stays close to the build.

PlinthWeb keeps senior judgment in the work from the first audit through launch. You have a direct owner for decisions, scope, feedback, and delivery instead of passing context between a sales team, project queue, and anonymous production line.

Specialists can support a defined need such as photography, identity design, legal review, or advanced integration work. Their role, cost, and responsibility are agreed before they enter the project.

  • One direct point of accountability
  • Senior review of strategy, design, and implementation
  • Visible decisions, dependencies, and acceptance points
  • Specialist support only when the scope calls for it
02

What custom-coded means

Purpose-built decisions from the first page to the final component.

Custom-coded does not mean ignoring proven software. We use maintained frameworks, libraries, hosting services, and content systems when they are the right engineering choice. The information architecture, components, behavior, and integrations are implemented for your requirements.

The deliverable is maintainable source code and a coherent design system—not a one-click generator output, a no-code dependency, or an off-the-shelf theme with a new logo.

  • No no-code page-builder dependency
  • No recycled off-the-shelf theme
  • Clear technical choices and ownership boundaries
  • Reusable components for consistent future pages
03

Custom business applications

Build the internal system your operation actually needs.

A focused business application can replace disconnected spreadsheets and fragile handoffs with one model for customers, work, decisions, and reporting. Possible scopes include CRM, customer portals, scheduling and dispatch, estimates and invoices, inventory, work orders, dashboards, approvals, documents, integrations, and field tools.

Discovery tests whether custom development is justified or whether an existing product should be configured or integrated instead. When a build makes sense, delivery starts with the smallest complete workflow, validates it with representative users, and adds later capabilities from operational evidence.

  • CRM, portals, scheduling, dispatch, estimates, and work orders
  • Inventory, dashboards, approvals, documents, and field tools
  • Role-based access, migration, integrations, and recovery planning
  • Phased delivery with security and accessibility in the scope
04

Business workflow automation

Remove repeated administration without hiding important decisions.

Automation can connect forms, inboxes, calendars, spreadsheets, CRM records, task systems, documents, notifications, and approvals when the underlying rules are stable. We map the current process, exceptions, owners, and system of record before choosing triggers or moving live data.

Human review remains where judgment, money, privacy, or public communication creates risk. Production flows include validation, visible failures, safe retries where appropriate, alerts, recovery steps, credential ownership, and documentation so a broken connection does not silently lose work.

  • Process, trigger, data, owner, and exception mapping
  • Forms, records, documents, notifications, and approvals
  • Human checkpoints for consequential actions
  • Failure handling, monitoring, and change ownership
05

Strategy, content, and brand

Shape the argument before styling the screens.

We clarify the audience, offer, objections, proof, service area, and next action; inventory useful existing content; then shape the sitemap, page responsibilities, message hierarchy, and writing brief. Copy can be edited collaboratively or written as a separate agreed scope.

The visual system grows from that structure. Existing identity assets can be refined for digital use, while naming, full identity programs, photography, and illustration remain optional specialist scopes rather than hidden line items.

  • Offer and audience clarification
  • Content inventory, sitemap, and page outlines
  • Collaborative copy shaping or separately scoped writing
  • Optional digital brand refinement and creative support
06

Audit, migration, and quality

Find the risk before the new site inherits it.

For an existing site, the work can begin with a focused audit of content, search visibility, analytics, page speed, accessibility signals, forms, indexation, and technical dependencies. The result is a prioritized plan that distinguishes what to keep, repair, replace, redirect, and measure.

Before launch we test responsive layouts, browsers, keyboard paths, readable states, motion preferences, forms, metadata, analytics events, and integrations. Redesigns include an agreed redirect and migration plan so useful URLs and content are not discarded casually.

  • Website, search, content, and analytics audit
  • Accessibility-minded responsive and keyboard QA
  • Redirect map and controlled content migration
  • Forms, metadata, integrations, and launch checks
08

Google Business Profile operations

Keep the public profile accurate without putting it on autopilot.

The monthly operating plan can schedule approved posts, maintain services and hours, check categories and attributes, organize image updates, add measured links, and support a compliant review-request workflow.

Automation handles the repeatable steps. Public claims, sensitive replies, and review responses remain human-approved. We do not fabricate engagement, purchase reviews, or promise map-pack placement.

  • Approved post and service-update calendar
  • Hours, category, attribute, image, and link checks
  • Compliant review-request workflow
  • Human approval for public responses
09

Strategy, social media, and paid campaigns

Give every digital channel a defined job and decision path.

Digital marketing strategy connects audience, offer, customer journey, website, organic search, content, social media, paid campaigns, conversion, and measurement. The plan assigns channel roles, owners, approval requirements, production capacity, budgets, and priorities instead of spreading the same message across every available platform.

Social management can cover planning, creative production, publishing, and bounded moderation; pay-per-click work can cover campaign structure, targeting, exclusions, advertisements, landing pages, conversion tracking, budgets, and reporting. Public claims and sensitive responses remain reviewed, media spend stays explicit, and commercial outcomes are never guaranteed.

  • Audience, offer, journey, channel, and measurement strategy
  • Social content planning, production, approval, and moderation
  • Paid-search or paid-social campaigns and landing-page alignment
  • Transparent budgets, attribution limits, and reporting
10

Managed hosting and care

Give the production website an accountable owner.

Managed care covers deployment, domain connection support, SSL, availability checks, backups or recovery options suited to the platform, routine dependency maintenance, and a defined allowance for small content changes. A move from an existing host includes a scoped migration and redirect plan.

The agreement names what is monitored, what counts as routine care, and what requires a separate project. Domain fees, paid services, large redesigns, and unsupported third-party code are not quietly folded into the plan.

  • Production deployment and domain support
  • Availability, form-path, and dependency checks
  • Recovery path for the supported website
  • Clear boundary between care and new development
11

Monthly optimization

Choose the next useful improvement instead of waiting for a redesign.

A monthly cycle reviews available search, speed, accessibility, content, and conversion evidence, then completes one agreed improvement within the plan. That may be a stronger service page, a clearer inquiry path, a performance fix, or a measured content update.

The backlog stays visible, work is bounded, and larger features are estimated separately. The goal is disciplined progress—not an unlimited retainer or a stream of decorative changes.

  • Monthly evidence and priority review
  • One bounded improvement cycle
  • Search, speed, accessibility, content, or conversion scope
  • Completed-work summary and next actions
12

Ownership and handoff

Know what you own, what is monitored, and what happens next.

The proposal defines deliverables, dependencies, deployment responsibilities, content responsibilities, and post-launch options before the build begins. At handoff, we document the parts your team needs to operate.

If the site includes an editing system, the authoring model fits the content instead of exposing raw layout controls everywhere. Ongoing maintenance remains a separate, explicit scope.

  • Documented scope and acceptance points
  • Source-code and deployment handoff defined in the agreement
  • Content editing matched to your team
  • Optional maintenance scoped separately

How the work moves

A visible path from business problem to measured improvement.

The activities change across websites, applications, automations, and campaigns, but the decision sequence keeps strategy, delivery, validation, and ongoing ownership connected.

  1. 01

    Discover

    Audit what exists and clarify users, audiences, offer, workflow, goals, evidence, data, constraints, integrations, budget, and responsibilities.

  2. 02

    Architect

    Define the content, journeys, data, channel roles, permissions, conversion actions, technical approach, and smallest useful scope.

  3. 03

    Design and prototype

    Make important interfaces, messages, creative directions, and user journeys tangible enough for informed review.

  4. 04

    Build and connect

    Implement the approved website, application, automation, content, campaign, tracking, and integrations included in scope.

  5. 05

    Validate and launch

    Test representative and exceptional paths, access, data, accessibility, performance, content, measurement, budgets, and integrations before release.

  6. 06

    Operate and improve

    Monitor the agreed service, review useful evidence, document changes, and prioritize the next operational, marketing, or product improvement.

Questions about PlinthWeb services

Do you use a no-code website builder or a premade theme?

No. This service produces a custom-coded implementation and does not depend on a no-code page builder or recycled theme. We use professional frameworks and tools where they improve quality and maintainability.

Do you help shape the content and brand direction?

Yes. Every project includes content structure and message hierarchy. Editing, full copywriting, photography, illustration, naming, or a larger identity program is included only when the proposal names that scope.

Can my team edit the website after launch?

Yes, when editing is part of the scope. We can connect a suitable CMS and model the content your team changes, or provide a code-first handoff.

Can it connect to our CRM, scheduler, or other services?

Yes, when an appropriate integration exists and is included in the proposal. Data ownership, authentication, failure handling, and maintenance responsibilities are defined before implementation.

How long does a custom website take?

Timing depends on page count, content readiness, feedback cycles, integrations, migration needs, and launch constraints. The proposal identifies milestones and dependencies after discovery.

Can you migrate an existing website without losing every URL?

Yes. Redesign work can include content inventory, redirect mapping, analytics baselines, domain and hosting coordination, and controlled release checks. The migration depth depends on the current platform and is scoped before implementation.

Can PlinthWeb manage social media and paid advertising?

Yes, through a defined channel, content, campaign, approval, budget, moderation, and reporting scope. Advertising spend, original photography or filming, influencer work, public relations, continuous community coverage, and specialist regulated review remain separate unless the proposal explicitly includes them.

Do you guarantee search rankings or business results?

No. We implement sound technical and content foundations, but rankings and commercial outcomes depend on competition, content, authority, offers, market conditions, and continued work.

Start with the brief

Tell us what needs to work better.

Share the audience, current website or system, workflow, channels, content, integrations, evidence, and constraints. We will use that context to define a sensible discovery or implementation step.