Lake OswegoAgency

How a project runs

Six steps, in order.

Each step ends with something you can hold. Swipe the strip, use the buttons, or press the arrow keys while the strip is focused.

Step 1 of 6: Listen

  1. Step 1

    Listen

    We do
    Read your brief, look at what you already have, and ask the questions it leaves open. We want the real problem, not the first one named.
    You do
    Send the brief and tell us plainly what is working and what is not. The brief builder takes about as long as a cup of tea.
    You get
    A short written summary of what we heard, with the open questions marked so nothing is assumed.

  2. Step 2

    Frame

    We do
    Draft the positioning: who this is for, what it stands on, how it should sound. We argue each line until it earns its place.
    You do
    React. Cut what is wrong, correct what is close, and say what we missed. Disagreement here is cheap and useful.
    You get
    A one-page frame that every later decision is checked against.

  3. Step 3

    Name and mark

    We do
    Explore a few genuinely different routes for the name and the mark, each with its reasoning laid out beside it.
    You do
    Choose a direction, or tell us which parts of two routes belong together. Gut reaction counts as data.
    You get
    A chosen route, refined into a name and a mark that can stand on their own.

  4. Step 4

    System

    We do
    Build the working parts: a palette checked for contrast, a type pairing with fallbacks, a grid and the rules for using them.
    You do
    Test the system against the real things you make. Tell us where it pinches.
    You get
    An identity guide and the asset files, ready for the people who will use them.

  5. Step 5

    Make the site

    We do
    Design the pages, write the copy with you, and build it in clean markup. We test by keyboard, on a phone, and with reduced motion.
    You do
    Supply real content and review the work as it appears. Real words break layouts that placeholders never do.
    You get
    A working site that loads fast, reads well at any width and behaves for everyone.

  6. Step 6

    Hand over

    We do
    Run final checks, launch, and write down how everything works. We stay reachable while the site settles in.
    You do
    Sign off, and keep the accounts and domains in your own name. Ownership should never be a question.
    You get
    Files, notes and a clear way to reach us, with the option of ongoing care.

Pace depends on scope and on how quickly decisions get made. We agree a rhythm at the start, and we tell you early if it needs to change.

Ground rules

How we keep it moving.

What we need from you

A brief, honest answers, and decisions made by people who can actually make them. The fastest projects have one clear voice on the client side.

  • A short written brief, or the one from the builder
  • Access to whatever already exists, even if it is rough
  • Real content for the site, in whatever state it is in
  • Feedback that says what is wrong, not only what to change

What you can expect

Work shown with its reasoning, feedback gathered in rounds that each have a purpose, and plain answers when something is not working.

  • Reasons beside every recommendation
  • Contrast, keyboard and reduced-motion checks built in
  • Notes written for the next person who touches the work
  • No surprises about scope; changes are discussed first

What stays yours

Everything we make for you. Accounts, domains and files are held in your name from the start, so the work is portable the day it is finished.

  • Source files and exported assets
  • The site code, documented and host-agnostic
  • The guide that explains the identity
  • The freedom to take it elsewhere, any time

Start with step one.

The brief builder covers the questions we would ask first. Fill in what you can; leave the rest.

Build your brief