Blog

  • Why page twenty should look like page one.

    Decide once

    Colours, type sizes, spacing, corner shapes, how a button behaves. When those are decided once and stored as named values, every new page draws from the same source instead of someone’s best guess.

    One change, everywhere

    If the brand colour shifts a shade, it should change in one place and appear on every page, every email and every app screen at once. Without a shared system, that same change means a week of hunting.

    It is how one studio runs many brands

    Modolla and Ember & Grain look nothing alike — a finance app and a fine-dining restaurant — yet they are built on the same underlying system. Each brand sets its own values; the structure underneath stays the same. Each brand gets its own look, and nothing has to be rebuilt to get it.

    What you get to keep

    A design system is not decoration. It is the part of the project that keeps paying back, because the twentieth page costs a fraction of the first and still looks like it belongs.

  • Your domain, your accounts, your keys.

    The domain is yours

    Register it in your name, on an account you can log in to. A studio can manage the settings, but the registration should never depend on a relationship staying friendly.

    So is the money

    Payments run through a merchant account you own. Fees, payouts and customer refunds are between you and the provider. A studio wires the checkout to it; it does not sit in the middle of your revenue.

    Hosting and content, too

    Your site should live on hosting you can see, with content in a system you can edit without asking permission. If you ever want to take the work elsewhere, the move should be a handover, not a rescue.

    Write the list at the start

    Before anything is built, list every account the project will touch and whose name it sits in. It takes ten minutes. It saves the awkward conversation two years later when someone has left and nobody can find the password.

  • Sell one product properly before you list a hundred.

    Follow one item all the way

    Choose a product people actually buy. Take it from the collection grid to its own page, into the cart, through checkout and into the confirmation email. Every gap you find there would have appeared a hundred times over.

    The questions live on the product page

    Sizes, materials, what arrives in the box, when it ships and what happens if it does not fit. When those answers sit next to the button, fewer people leave to ask and fewer orders come back.

    The cart should remember

    People browse on a phone at lunch and buy on a laptop at night. A cart that survives a closed tab is not a luxury. It is the difference between an order and an abandoned visit nobody ever sees.

    Then scale the pattern

    Once one product works end to end, the rest of the catalogue is a matter of good data rather than new design. It is the order we work in on our own storefronts, and it is why their pages do not drift apart as they grow.

  • Why we build the first screen before we write the proposal.

    Pictures of websites mislead

    A static mockup always looks finished. It has no slow connection, no long product name, no thumb trying to reach a button at the bottom of the screen. The problems that matter only appear when the thing is real and in your hand.

    Pick the screen that earns the money

    For a shop it is the product page. For a photographer it is the booking step. For an app it is the moment a new user first sees their own information. We build that one screen properly, on a link you can open anywhere, before anything else is scoped.

    Then the proposal gets honest

    Once you have used one real screen, the conversation changes. You stop asking what it will look like and start asking what it should do next. The scope that follows is shorter, clearer and closer to what you actually need.

    What it does not mean

    One screen is not the product, and it is not a free sample of the whole build. It is the cheapest way for both of us to find out whether we see the same thing before anyone commits to a timeline.

  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

  • Five things to have ready before you brief a studio.

    Who it is for

    Not a demographic — a person. The customer who already loves you, and why. Every design decision gets easier when there is one real person to design for.

    The one job

    What must a visitor be able to do? Book, buy, ask, sign up. Pick one. A site that tries to do five things equally does none of them well.

    What exists already

    Domains, logins, an old site, a product spreadsheet, the payment account. Knowing what is there stops a studio from rebuilding what you already own.

    Three sites you envy

    Not to copy. To show what ‘good’ looks like to you. The reasons you give — ‘it feels calm’, ‘I found the price fast’ — are more useful than the links.

    A rough budget band

    It is not a negotiating move. It tells the studio whether to propose a focused first release or a complete build, and saves you both a round of guessing.

  • A beautiful homepage is only the beginning.

    Follow one real task

    Pick a reason a customer would visit: book a portrait session, ask about a menu, find a jacket in the right size. Walk that task through every screen. A strong first impression should lead to useful detail, a clear next step and an honest confirmation.

    Answer the small questions

    Service areas, preparation, lead times and what is included often matter more than another paragraph about excellence. If a visitor has to leave to ask a basic question, the page has more work to do.

    Make the handoff clear

    A submitted inquiry is not a confirmed appointment. A draft plan is not a purchase. Say exactly what happened and who acts next. That small distinction is part of the experience, not a footnote.

    Build for the second visit

    People return with a different question. Give each service, project or article a useful address they can save and share. A site with real depth makes those return visits worthwhile.

  • A concierge needs a good first day, too.

    Start with the facts

    Write down what you sell, where you work, when you are available and what happens after someone makes an inquiry. Missing information cannot become a reliable answer. If a price varies, explain what determines it rather than supplying a convenient guess.

    Give it a boundary

    Separate questions it can answer from decisions a person should make. Your published opening hours are an answer. A refund outside the policy is a decision. The handoff should tell the customer what happens next without promising an unconfirmed response time.

    Teach it your voice

    Collect three examples of how you explain your work well. Add phrases you would never use. Concrete examples help more than asking for a friendly or professional tone, because those words mean different things to different businesses.

    Keep the source current

    Whenever you change a service, update the information it uses. Read the unanswered questions regularly. They are a map of what your customers need and your website may be missing.