Skip to content

Build Lab

Websites, apps and CRMs that work together

We design and build websites, mobile apps and custom CRMs, then connect them to the systems you already use. You review each stage on a working build before the next begins.

Interactive prototype · Illustrative records; no data is sent

Click to try · Choose a workflow step, then simulate a request to follow the record.

Fernhollow sales desk

Try it yourself — choose a view, then follow the steps. Your actions update the interface.

Fernhollow sales desk. The demo request from the website arrives, is assigned by rule, gets a follow-up and pings the owner’s phone.

From idea to working product

A brief becomes screens, the screens connect to the systems you run, and you test a working build before it ships.

Interactive product workflow

01 / 04

A clear brief

Set the users, the job and the acceptance criteria before the first screen is built.

brief.acceptance = agreed

Interactive prototype · Illustrates the build process.

What you can check on every build

  • Every stage is tested on staging against criteria you approved
  • Defects are logged with severity, fixed and retested before a milestone is accepted
  • Accessibility and performance targets are written into the criteria and checked on the browsers and devices in scope
  • Access to your systems is limited to what the work needs and returned at launch
  • Handover covers code, documentation and admin access, as set in your statement of work

How an engagement runs

  1. Discovery

    Users, scope and constraints documented; milestone plan and acceptance criteria agreed.

  2. Design

    You review wireframes or interface designs while changes are still inexpensive.

  3. Build in milestones

    Each milestone ends with a staging demo and a check against its criteria.

  4. Testing

    Tested on the browsers and devices in scope; every defect tracked to resolution.

  5. Launch and handover

    Deployed to the agreed environment; code, documentation and access handed over as set in your statement of work.

Milestone acceptance report

Illustrative deliverable
Milestone
Quote request form and CRM delivery
Acceptance criteria
Required fields validated · Submissions reach the CRM test account · Works on the browsers and devices in scope
Demo
Staging demo held with your project lead
Defects
Two found during the demo, both fixed and retested
Sign-off
Accepted in writing; next milestone starts
Illustrative milestone report; values are examples.

What a milestone report looks like

Every milestone ends with a report like this, checked against criteria you approved before the work began.

Need buyers for the product you're building? See Revenue Engine

Questions buyers ask

How are milestones defined and accepted?

In discovery we write each milestone's deliverables and acceptance criteria together. At the end of each milestone you see a staging demo, and we check the work against those criteria before the next one starts.

Can you connect to the systems we already use?

Yes, where those systems allow it. Integrations are scoped in discovery, mapped field by field, and the systems in scope are listed in your statement of work.

Who owns the code and accounts?

Ownership, IP and handover terms are set in your statement of work, agreed before work starts.

What happens after launch?

We support the live software for the period set in your statement of work. Ongoing maintenance can be agreed separately.

How do you choose the technology?

In discovery, based on your product, your team and the systems it must connect to. The choice is recorded in the discovery document.

How do we work together day to day?

You get a named point of contact, a written report at the end of each milestone and review meetings at the cadence set in your statement of work.

Tell us what you need built

We reply by email to set up a scoping call, then send a discovery plan and milestones in writing.