Skip to content
The Stacklumen platform is in private alphaSee the products

Six steps. Written down. Shipped on a clock.

Every engagement is scoped in writing before it starts and runs on a weekly demo, so you always know where the project is. Here is what that looks like, step by step.

Send a brief Read the terms
Each engagement is a project in the Hub: the stages, the weekly demo and the thread in one place. Northwind is an illustrative client.

From brief to launch, and the 60 days after.

One team scopes it, builds it and supports it. You always know which step the project is on and what happens next.

  1. Brief

    Reply in one business day

    You send a short brief through the contact page: what you are building, who it is for, the constraints. No discovery deck. We read it the day it arrives and reply by the next business day, including when the answer is no.

    • The goal, in a line
    • Audience, timeline, budget range
    • Anything we should know up front

  2. Scope

    Proposal in 3 business days

    If we are a fit, a written scope follows: deliverables, timeline, fee, payment schedule, and what is deliberately not included. A real number, not a range. Sign it as it is or send revisions; either way it is signed within a week.

    • Fixed fee or retainer, in writing
    • Milestones tied to demos, not hours
    • 60 days of post-launch support included

  3. Kickoff

    Day 1

    Once it is signed you get a project in the Hub with a shared thread and a tracker, and one kickoff meeting where we walk through the plan. Everything after that meeting is written down.

    • Hub project and thread set up
    • Repository, design files and deploys ready
    • Weekly demo day agreed

  4. Build

    Weekly demos

    You follow progress on a staging link we share every week, and leave feedback on the build itself rather than in a separate document. We push work every business day, so the staging link is always current.

    • Weekly demo on a staging URL
    • Feedback threaded on the work
    • Replies inside one business day

  5. Launch

    Cut-over day

    Launch day is calm. We rehearse the cut-over with you the week before, hold a 30-minute go window, then monitor the first 48 hours and fix anything that breaks in real time.

    • Rehearsal the week before
    • Active monitoring for 48 hours
    • A signed sign-off records the launch state

  6. After

    60 days included

    Every engagement includes 60 days of post-launch fixes, copy changes and small adjustments. After that, move to a monthly support agreement, hand over to your in-house team, or wrap cleanly. We will say which we think makes sense.

    • 60-day fix window included
    • Optional support retainer after that
    • Documentation handed over either way

Scoped in writing, before anything starts.

Every proposal names what it covers and what it deliberately does not, and every engagement runs on our published services terms. Read who owns what before the first conversation.

Written first
Scope, timeline and fee are signed before kickoff. Mid-project surprises are ours to absorb, not yours.
Named exclusions
Every proposal lists what it does not cover, so the answer arrives before you sign rather than in week five.
Ownership
Code, repositories, accounts and documentation transfer to you at handover. Nothing is held back to keep you on a retainer.
One team
The people who scope the project are the people who build and support it. There is no hand-off to a delivery team.
Read the terms See pricing
The services terms, open at who owns what.

Eight commitments on every build.

Client sites are built in Terminal, set up for the team that will run them. Applications, portals and integrations are built in Astro and React. Whichever it is, every build ships with these.

Editable without code

Your team changes copy, images, pages and sections from the editor, with no developer in the loop.

Search and answer engines

Titles, meta, structured data, sitemaps and canonicals are set in the build and editable from the dashboard.

Speed, measured

We report Core Web Vitals and tune against the published thresholds, and treat speed as a deliverable.

Integrations

POS, CRM, marketing and analytics tools connect to the site, so it is the hub your tools feed rather than an island.

Commerce

Ecommerce set up with the tooling to grow from the first sale to serious volume.

Accessible by default

Built and checked against WCAG, so every customer can use what we build.

Brand, digitised

Marks vectorised and colour and type set as tokens, so the brand renders the same on every surface.

Brand-first builds

You see a real, on-brand build early in the project, and it sharpens from there.

Ready for step one? Send a brief.

Websites from $3,000. Applications from $15,000. A reply within one business day, and a written proposal in 3 business days.

Send a brief See pricing
How long does an engagement take?
From brief to signed scope is usually under a week. Websites, built in Terminal, take two to six weeks; custom applications take six to sixteen; support retainers are open-ended.
Do you sign before starting work?
Yes. Every project has a written scope with a fixed fee or retainer rate, milestones tied to demos and a payment schedule, signed by both sides before kickoff.
What does post-launch support include?
Sixty days of bug fixes, copy changes and small adjustments. After that you can move to a monthly retainer, take the project in-house with a clean handoff, or wrap.

Image notice. Some imagery on this site may be owned by or associated with third-party platforms our client sites have been built on. Stacklumen claims no creative ownership or intellectual property rights over those images; all rights stay with their holders. Rights holders can ask for removal or different attribution at support@stacklumen.com, and we respond promptly.

Made inTerminal