Skip to content
Orvenant
Orvenant

Ways to work with us

Choose a working relationship that fits the work.

A defined project, ongoing development or support for your agency. Agree the scope, responsibilities and decision process before choosing the delivery model.

Start with the business need

Some work has a clear finish line, such as a website release or migration. Other needs involve a changing backlog, care for a live service or a team working alongside yours. The delivery model should follow that difference. Before choosing an arrangement, describe the outcome, current system, decisions still open and who will own the result after the first release.

Find the right direction

Each arrangement answers a different operating question. The proposal should state capacity, responsibilities, review points and commercial terms for the option selected.

A defined project

Choose an agreed scope when deliverables, acceptance criteria and a handover can be described before work begins. Changes then need an explicit review path.

Explore A defined project

Continuing development

Use a prioritized working relationship when a live service needs maintenance and planned improvement. Capacity, coverage and exclusions are written into the agreement.

Explore Continuing development

Collaborative delivery

A dedicated team or agency relationship can suit a continuing roadmap or a client-facing partner. Decision ownership and communication boundaries matter as much as technical skills.

Explore Collaborative delivery

What the first conversation should cover

Tell us which people use the current system, what is not working and what you hope will change. Identify relevant content, providers, deadlines and approval owners. You do not need to settle the technical approach first. We can compare a focused project with continuing work and make the unanswered decisions visible before either side assumes a price or delivery date.

A clear basis for the next step

There is no single public package that can define a project, support relationship or team arrangement. Scope and price depend on the work and responsibilities agreed. A proposal should show what is included, what your organization supplies and how completion or continuing coverage is assessed. Contact hi@orvenant.com to discuss the starting point.

Some of the teams we have worked with.

Across talent, fitness, mobility, payments and local commerce.
RandstadClassPassVeezuRushpaySupport Black Owned

Questions before we start.

How do we choose between a project and ongoing support?

A project fits a defined outcome with acceptance and handover. Continuing support fits a live service with an evolving backlog and agreed capacity. The first conversation can separate immediate fixes from longer-term improvements before selecting either model.

Can an engagement change shape later?

It can be discussed, but the effect on scope, capacity, responsibilities and commercial terms should be agreed explicitly. A project should not silently turn into unlimited maintenance, and a retainer should not become an undefined build commitment.

A DIRECT CONVERSATION

Bring us the problem. We’ll work through the next step.

Share what exists today and what you want to change. We can discuss the scope, dependencies and a practical way forward.

Privacy settings

Optional Google Analytics measures page visits and contact-option use. Rejecting keeps Analytics off. Accepting allows analytics cookies. Advertising features stay off, and enquiry contents and contact details are not sent to Analytics.

Withdrawing stops future collection and removes this site’s accessible Analytics cookies. It does not erase information already received by Google. Privacy notice · Cookie notice