Welcome to the Stacklumen app·Your home for web development
How we work

Six steps. Written down. Shipped on a clock.

We don't do exploration phases. Every engagement is fixed-scope, written down before we start, and runs on a weekly demo cadence so you always know exactly where the project is. Here's what that actually looks like.

Send a brief Or book a 15-min call
  1. 01

    Brief

    ~ 24 hours

    You send us a short brief — what you're building, who it's for, the constraints. Either via /contactus or a quick Calendly call. No discovery deck, no "tell us your dreams." We read it the same day and respond by the next business day.

    • One-line summary of the goal
    • Audience, timeline, budget range
    • Anything we should know up front
  2. 02

    Scope

    ~ 48 hours

    If we're a fit, we send back a written scope: deliverables, timeline, fee, payment schedule. No ranges, no "starting at." A real number. You sign it as-is or come back with revisions; either way we sign it within a week so the project doesn't bleed into "exploration."

    • Fixed-fee or retainer, written down
    • Milestones tied to demos, not hours
    • 60-day post-launch support included
  3. 03

    Kickoff

    Day 1

    Once signed, you get a shared chat channel (in the Hub portal or Slack — your call), a project tracker, and an introductory meeting where we walk through the plan. Everything is written down. The kickoff meeting is the only meeting that gets recorded by default.

    • Hub portal + chat channel provisioned
    • Repo, design files, deploy pipeline set up
    • Weekly demo cadence agreed
  4. 04

    Build

    Project duration

    We build. You watch progress on staging URLs we share each week. Feedback happens in-context — directly on the build, not as Loom-and-email back-and-forth. We push every business day; you're never wondering "are they actually working?"

    • Weekly demo on a staging URL
    • In-context feedback, threaded on deliverables
    • Slack/chat replies inside one business day
  5. 05

    Launch

    Cut-over day

    Launch day is calm. We rehearse the cut-over with you a week prior, hold a 30-minute "go" window, and stick around for the first 48 hours actively monitoring. If anything breaks, we fix it in real time. No "see you in our next engagement."

    • Pre-launch rehearsal week before
    • Active monitoring for the first 48h
    • Signed sign-off captures the launch state
  6. 06

    After

    60 days included

    Every engagement includes 60 days of post-launch support: bug fixes, copy tweaks, small adjustments. After that we either retain you on a monthly support agreement, hand you off to your in-house team, or wrap with a clean exit. Your call — we'll tell you which we think makes sense.

    • 60-day post-launch fix window included
    • Optional support retainer after that
    • Clean documentation handoff either way
Principles

Why it works.

01

Written before we start

Scope, timeline, and fee are written down and signed before kickoff. Mid-project surprises are our problem to absorb, not yours.

02

In-context feedback

You leave comments on the build, not in a doc that gets transcribed later. The work itself is the source of truth.

03

Same-day visibility

Every business day we push something. You can always check the staging URL and see where the project is.

04

Same team start to finish

The people who scoped your project are the ones who build it. No "handing off to delivery." No bait-and-switch.

Q3 2026 — accepting briefs

Ready to start step one?

Send a brief or grab a 15-minute slot. We respond within one business day.

Send a brief Book a call
Deployed with Webflow