Skip to content
Rynvo Logo
/// ENGAGEMENT PROTOCOL

HOW THE WORK ACTUALLY RUNS.

Six stages, published in advance. No discovery gauntlet, no account manager relaying messages, and no phase where the project goes quiet and you find out later it went sideways.

BOOK AN INTRO CALL >>> SEND DETAILS INSTEAD >>>
[ SEE PRICING ]
/// STAGE SEQUENCEFIRST CONTACT TO ONGOING SUPPORT

YOU ALWAYS KNOW WHICH STAGE YOU ARE IN

  1. STAGE 01

    ASSESSMENT

    WITHIN 24 HOURS

    You send the site and the goal. We look at it properly — architecture, performance, what is leaking, what is worth keeping — and write back with what we actually think. Sometimes that answer is that you do not need us, or that the problem you described is not the problem you have. There is no charge and no obligation attached to this stage.

    YOU GET
    A written assessment, not a brochure
    WE NEED
    A URL and one sentence about the goal
  2. STAGE 02

    SCOPING CALL

    45–90 MINUTES

    A working call with the people who would build it — not a sales team. We map what exists, what the goal is, what systems have to be integrated with, and what is genuinely in the way. Constraints surface here: your compliance review, your ERP, your enrolment calendar, the internal politics around who owns the homepage.

    YOU GET
    A shared understanding of the real scope
    WE NEED
    A decision-maker on the call
  3. STAGE 03

    FIXED SCOPE & PRICE

    2–5 DAYS AFTER SCOPING

    You get the scope written down and a fixed number against it, on paper, before anything starts. What is included, what is explicitly not, what it costs, and how long it takes. If we think part of what you asked for is a bad investment, that is in the document too, with the reasoning.

    YOU GET
    Fixed price and timeline in writing
    WE NEED
    Sign-off, or the questions that stop you signing
  4. STAGE 04

    BUILD

    SET AT STAGE 03

    Work happens in visible increments against a staging environment you can look at whenever you want. You are not waiting for a reveal. Direct access to the engineers, a standing check-in at whatever cadence suits you, and no phase where the project goes quiet. Scope changes get priced as they arise rather than absorbed silently and resented later.

    YOU GET
    A staging URL from week one, and access to the people building it
    WE NEED
    Content, credentials, and timely decisions
  5. STAGE 05

    LAUNCH

    PLANNED, NOT IMPROVISED

    Redirects mapped, analytics verified, structured data validated, performance and accessibility measured, and a rollback path that exists before it is needed. Launches are scheduled when someone is available to watch, never at 5pm on a Friday. Where rankings are at stake, migration is treated as its own discipline.

    YOU GET
    A launch plan, verified metrics, and a rollback path
    WE NEED
    DNS access and a date that suits your business
  6. STAGE 06

    AFTER LAUNCH

    ONGOING, IF YOU WANT IT

    This is the stage most agencies skip. Monitoring, patching, and iteration based on what real traffic does rather than what the mockup assumed. You are not obliged to keep us — you own the code and the documentation to hand it to anyone. We would rather keep the work by being useful than by making leaving expensive.

    YOU GET
    A site that keeps working, and the option to walk
    WE NEED
    Nothing. That is the point
/// STANDING RULES

HOW WE OPERATE THROUGHOUT

ACCESS / DIRECT

YOU TALK TO WHO IS BUILDING IT

No account manager, no relay layer. The person answering your question is the person who wrote the code, which means the answer is accurate and arrives the same day rather than after an internal round trip.

SCOPE / FIXED

A NUMBER, NOT A RANGE THAT DRIFTS

You get a fixed price against a written scope. Change requests are priced when they come up, so nothing is quietly absorbed and then invoiced as an overrun or, worse, resented and delivered badly.

VISIBILITY / STAGING

THERE IS NEVER A BIG REVEAL

A staging environment exists from the first week and you can look at it any time. Surprise is a failure mode. If something is going in a direction you dislike, we would much rather hear it in week two than week nine.

CANDOUR / DEFAULT

WE TELL YOU WHEN YOU ARE WRONG

If a request will not achieve what you want, we say so, explain why, and propose the alternative. You may overrule us and we will build what you asked for — but you will have heard the argument first.

OWNERSHIP / CLEAN

YOU OWN THE CODE AND THE KEYS

Code, content, infrastructure configuration, and the documentation to hand it all to another team are deliverables. No proprietary lock-in, no hosting arrangement designed to make leaving painful.

PROOF / MEASURED

CLAIMS COME WITH NUMBERS

Performance, accessibility, and search claims are measured before and after, and you get both sets of figures. An assertion nobody verified is marketing, and this whole site argues against that.

/// CLIENT SIDE

THE PART YOU OWN

Projects rarely slip because the build was hard. They slip because a decision sat unmade for three weeks, or because content that only your team could write never arrived. We would rather say that plainly at the start than discover it in week seven.

What we need is small but non-negotiable: one person empowered to make decisions, access to the systems we are integrating with, and content — or an honest admission that you want us to write it, which we scope as work rather than assume as a favour.

In exchange you get an unusual amount of access. You talk to the people writing the code. There is no account manager translating your requirements into a brief and translating our answers back into reassurance.

/// FIELD REPORTS

CLIENT TRANSMISSIONS

VERIFIED OPERATOR FEEDBACK // CLEARANCE LEVEL: PUBLIC

"Nicklaus was absolutely fantastic to work with. He completely transformed our website for The CPG Co-Op, and the end result is better than I could have imagined. What really sets Nicklaus apart is that he’s not just a great designer—he has a deep understanding of the technical side of websites and the backend functionality that makes everything work. He was able to take a fairly complex project, handle the technical details seamlessly, and still make the entire process incredibly easy for me as someone who is, frankly, a total luddite when it comes to this stuff. He also built the site in a way that makes it incredibly easy for me to manage and make changes myself, which means we aren’t constantly paying someone every time we need to update something. That was a huge win for us. He was responsive, collaborative, incredibly fast, and genuinely cared about getting it right. I would highly recommend Nicklaus to anyone looking for someone who can bring the creative vision and the technical expertise to actually execute it. He made the whole process easy—and delivered a website we absolutely love."

EMILY KEALEY

FOUNDER // THE CPG CO-OP

ON THE CPG CO-OP

Emily Kealey portrait
/// FIELD QUESTIONS

STRAIGHT ANSWERS

HOW LONG DOES A PROJECT TAKE?

A focused marketing site is usually measured in weeks. Anything with authentication, a system integration, or a formal compliance review runs longer, because the review cycle and the integration set the pace rather than the design work. You get a specific timeline at stage 03 — not a range that quietly expands.

WHAT IF WE NEED TO CHANGE SCOPE MID-BUILD?

Normal, and we would rather you did than sit on it. Changes are priced when they come up and you decide whether they are worth it. What we avoid is silently absorbing scope, which produces either a surprise invoice or a rushed job, and usually both.

DO YOU WORK WITH OUR EXISTING TEAM?

Frequently. In-house marketers, designers, and engineers are all common collaborators, and we would rather integrate with people who know your business than replace them. What matters is that the boundary of responsibility is drawn clearly at stage 03 so nothing important sits in the gap between two teams.

WHAT HAPPENS IF WE WANT TO STOP?

You get everything produced to that point — code, assets, documentation, infrastructure access — and you pay for the work completed. There is no clause designed to make leaving expensive. A client who stays because the alternative is painful is not a reference.

WHO ACTUALLY DOES THE WORK?

Our team, in the United States. Not a subcontractor, not an offshore shop operating under our name. You will know the names of the people building your system, and you can talk to them directly.

DO YOU SIGN NDAS?

Yes, routinely, and usually before the scoping call if the project is sensitive. Send yours and we will review it rather than insisting on our paper.

/// NEXT STEP

START AT STAGE 01.

Send the site and the goal. You get a straight assessment back within 24 hours — including whether we think the project is worth doing at all.

BOOK AN INTRO CALL >>> SEND DETAILS INSTEAD >>>