Web Development services

A better website. A more useful web application.

Website and web application development for US businesses. Salt builds business websites, customer portals, SaaS interfaces, and operational tools around the people who use them.

Where we can help

From business websites to connected applications.

Choose a focused engagement or combine the work your project needs.

Business websites & CMS

Create a responsive website with clear navigation, service information, reusable page templates, and manageable content. WordPress or a headless CMS can suit content-led sites; the choice depends on editing needs, integrations, and maintenance.

Custom web applications

Build authenticated experiences with user roles, forms, approvals, dashboards, and administration. Define permissions and exception states alongside the main workflow.

Customer portals & SaaS interfaces

Give customers or partners a workspace for records, requests, bookings, or product tasks. Scope account access, notifications, and connections to your existing services.

Redesigns & platform improvements

Improve an existing site or application while planning for content migration, redirects, analytics continuity, performance, and release risk. Start with the most important journeys.

Example starting points

Recognize your challenge?

These are illustrative examples, not the limit of what we can scope. Tell us about your own workflow.

01

A services business needs clearer enquiries

Organize its offer, add relevant project evidence, and connect enquiry forms to a dependable capture process.

02

A distributor needs a customer workspace

Let authorized users find account-specific records, submit requests, and see progress connected to an agreed data source.

03

A product team needs a first web release

Deliver a complete user journey with essential administration, integrations, and a plan for later features.

Relevant experience

See the work in context.

Explore our work

These projects span content-managed websites, custom portals, and marketplace applications. Review each scope to judge its relevance to your project.

What we agree to deliver

A scope you can review.

Your proposal identifies the selected outputs, exclusions, and acceptance criteria.

An agreed scope and architecture

Page or workflow inventory, user roles, integrations, content responsibilities, and acceptance criteria.

Working interfaces and integrations

Responsive frontend, required backend work, CMS configuration, and agreed external service connections.

Testing and release preparation

Checks for key journeys, browser and device behavior, form delivery, permissions, and agreed accessibility and performance requirements.

Handover and operating plan

Source code, deployment instructions, content guidance, and clearly defined maintenance and support responsibilities.

From brief to handover

Make decisions as the work takes shape.

How we work
  1. 01

    Define the important journeys

    Understand the audience, existing systems, content, and business goal. Separate essential launch requirements from later features.

  2. 02

    Design and build in reviewable stages

    Agree the structure and interface, implement the connected workflow, and review working increments with your decision owner.

  3. 03

    Test, release, and hand over

    Validate the agreed acceptance criteria, migration and redirects where needed, and who will own updates after launch.

Working with your US team

Agree US time-zone overlap, a decision owner, review cadence, and access before starting. Your proposal defines scope, fees, milestones, intellectual-property terms, and handover. Choose a defined project or discuss ongoing delivery support when your roadmap needs it.

Budget and timing

Estimate the work,
not just the page count.

The number of unique templates or workflows, user permissions, backend logic, integrations, content migration, and testing requirements shape the estimate. A content website and an authenticated business application need different delivery plans.

We confirm assumptions, dependencies, review rounds, and availability before proposing a schedule. Third-party costs and work after launch should be listed separately.

Discuss your web project

Before you begin

Web Development questions.

Tell us what you need

Start with the problem
you want to solve.

Share your current URL or product idea, who will use it, the most important task, and any systems it must connect to. A short brief is enough to begin.

Discuss your web project