Orthaviel Digital Orthaviel Digital
A strategist reviewing a landing page draft on a bright desk, screen angled away from the camera
Orthaviel Digital

What working together actually looks like

What working together actually looks like

What working together actually looks like

Engagements run in stages, and each one ends with something you can look at. No phase is meant to be a mystery, and you shouldn't have to ask what's happening next. Here's the arc, from the first call to the day the page goes live.

Start with a discovery call See case studies

Nine stages, start to launch

Every stage ends with something you can hold

  • Discovery and intake

    A conversation, not a proposal. We ask what the page is for, who it is aimed at, and what you want a visitor to do when they land. If a page is already running, we read it first.

  • Scope and written plan

    You get a short written scope: what is included, what is not, roughly when each stage lands, and the name of your main point of contact. It reads in one sitting.

  • Structure and content hierarchy

    Before any visual work we lay out the page's argument: what a visitor needs to believe to take the next step, and in what order. Most pages get shorter here.

  • Copy direction

    Headings and body copy carry the argument as much as the sections do, so we draft language and structure together. You react to a draft instead of filling in a questionnaire.

  • Wireframes and interface

    Wireframes settle structure before anyone debates styling, and they stay plain on purpose. Interface design follows on real content, reviewed at mobile width as well as desktop.

  • Build and QA

    Responsive behavior, form handling, tap targets, labels, error states, confirmation messaging. We test on the browsers and screen sizes your audience actually uses, and set the structure up so routine updates do not need a developer.

  • Launch and the first weeks after

    Launch is a checkpoint. Once the page is live you get the first real read on visitor behavior: where they scroll, where they drop off, which sections hold attention. That shapes the first round of adjustments.

  • Ongoing iteration

    A page that converts well in month one may not in month six, especially if the offer or the audience shifts. Iteration work is paced: make a change, watch what happens, decide what to keep.

The stages above are the whole arc. What changes between engagements is how long each one runs and how many rounds of review sit inside it — not the order.

Conversion hierarchy

Decide the argument before you decorate it

Structure is where most landing pages are won or lost. We map what goes above the fold, what earns a section of its own, and what gets cut — then we defend each decision against the offer and the audience instead of the other way round.

Two things tend to happen. Sections that existed because someone asked for them lose their slot, and the remaining copy gets sharper because it now has a job. Nobody has to argue about the color of a button yet.

A printed page outline spread across a light desk with several sections crossed out in pencil
The cut list from a real restructuring pass. Roughly a third of the original sections did not survive it, and the page read faster without them.

Copy direction

Headings and body copy carry the argument as much as the sections do, so we draft language and structure in the same pass. You see a draft you can react to rather than a questionnaire to fill in.

Edge cases are handled here rather than after launch: a visitor who is price-sensitive, a visitor who cannot tell which service fits them, a visitor comparing you to a competitor they already trust. If your team keeps brand voice guidelines, we work inside them.

First draft
Section headings, body copy, and the call-to-action language in one document, marked up so you can comment inline.
Revision rounds
Two structured rounds are standard. Additional passes are scoped, not metered by the hour.
Voice sources
Brand guidelines if they exist; your current site, decks, and sales emails if they do not.

Wireframes and interface

Wireframes settle structure before anyone debates styling. They are intentionally plain, because the point of the pass is to keep the conversation on what a visitor sees and in what order. Once that holds, interface design starts on real content rather than placeholder text.

You review the page at mobile width as well as desktop, because that is where most of your visitors will be reading it. Spacing, tap targets, and label sizes get checked at that width in the same session, not later as a fix.

Two designers comparing wireframe sheets against a phone held at arm's length in daylight
Layout pass at two widths. Plain sheets first, styling second — it keeps the review focused on order and hierarchy rather than color.
An engineer testing a page on three devices side by side across a bright studio table

Build, QA, and launch

The details only show up on a real device

The build covers responsive behavior, form handling, and the unglamorous details: tap targets, field labels, error states, and what a visitor sees right after they hit submit. We test on the browsers and screen sizes your audience actually uses — and we log what we tested, so you can see the coverage instead of taking it on faith.

If your team will maintain the page after handoff, we set the structure up so routine updates — a new headline, a swapped image, a price change — do not require a developer and do not break the layout.

Mobile first

Every stage is checked at small widths. Tap targets, labels, and line lengths get read the way a phone actually renders them.

Form handling

Field labels, validation messages, error and success states — walked through end to end, not just visually reviewed.

Fresh-eyes QA

Someone who did not build the page reads it cold and logs anything confusing, broken, or slow. Findings come back to you in plain language.

Launch day

Redirects, tracking, and the confirmation message verified together. Launch is a checkpoint, not a finish line — the first weeks after are part of the work.

The first weeks after launch

Once the page is live, you get the first real read on how visitors behave. Scroll depth, drop-off points, which sections hold attention and which ones never get a second glance. That data shapes the first round of adjustments.

We would rather plan for iteration from the start than treat launch as a one-time event. It is cheaper than a rebuild, and it works on the page you already paid for.

Two colleagues reading a scroll session together on a large screen turned away from the camera

Iteration, paced deliberately

Make a change, watch what happens, decide what to keep. Slower than rebuilding every quarter and considerably cheaper, with the page's own audience as the source of truth instead of opinion.

We bring a written read of the page and a short list of proposed changes. You decide which ones run. Nothing ships that you have not signed off on, and nothing is measured against a number we invented after the fact.

Who you actually work with

You get a named point of contact for the whole engagement, not a rotating queue and not a shared inbox. The same person sits in the discovery call, reviews the copy draft, and signs off on the build. When something changes, you hear it from them.

Around that contact sit the specialists a stage calls for — a writer, a designer, a front-end engineer — brought in when their part of the work starts and pulled back out when it is done. You are not paying for a standing team waiting for a task.

A consultant walking a client through a scoping document across a bright meeting table

What sits inside the scope

Included

  • Discovery, content hierarchy, copy direction, wireframes, interface design, build, and QA at the widths your audience uses.
  • A written handoff covering what was built, why it was built that way, and how to update the page without a developer.
  • The first weeks of post-launch reading and a short list of proposed adjustments.

Not included

  • Paid media buying, ongoing ad management, and platform ad accounts.
  • Photography or video shoots. We direct the shots and work from provided assets.
  • Third-party licenses, custom integrations, and anything that needs a procurement review before it can start.

Anything not on the included list is named in the scope document rather than discovered halfway through. If a stage turns out not to be needed, it stays out and the timetable shortens.

Questions before you commit

Three things people ask before the first call. If yours is not here, ask it directly and you will get a straight answer rather than a follow-up form.

Ask about your project
How long does a typical engagement take?

It depends on scope and on how quickly decisions get made on your side. A single landing page moves faster than a restructured site section with new brand work. You get a timetable with the scope, and it names each stage rather than a single vague end date.

Who do we work with day to day?

You get a named point of contact for the whole engagement, not a rotating queue. That person holds the schedule, answers most of your questions directly, and brings in a specialist only for the stage that needs one.

Do you need our brand guidelines?

They help. If you do not have them, we work from your existing site and materials, or we address positioning as part of the engagement. Either way, the copy direction stage is where the voice gets pinned down, so nothing is guessed at late in the build.

Two conversations and you will know if this fits

The first call is a working session, not a pitch. We read the page you have running, ask what it is for, and tell you plainly whether the scope you have in mind is worth building. If it is not, we say so.

Start with a discovery call See what we build

Studio hours

Monday to Friday, 9:00 AM – 6:00 PM · [email protected] · +1 215-591-5887

1201 Market Street, Suite 2200, Philadelphia, PA 19107