Services
AI automation for the work between your systems, and custom web applications, portals and websites for the people who use them. Commerce, mobile, search and hosting join the plan when the product needs them, and the first conversation needs no finished technical brief.
Illustration: three panels in a row. The widest shows AI automation as numbered workflow steps, with a person beside an approval seal; the next shows a custom web application screen for two roles; the last shows a website page with its next-step button. The two halves of the Orvenant bracket join on the first panel.
Most projects begin with one of four situations. Each door opens the service that fits, with a walkthrough or guide that shows how the work is done.
Requests are copied between tools, approvals are chased by email and nobody can say which record is right. AI automation and integration take that work over once the source of each fact and the responsible person are clear.
View AI & automationSee the walkthrough: Lead workflow walkthrough
People need roles, rules, records or a customer view that a collection of pages cannot provide. A custom web application or portal brings the workflow, permissions and data into one product.
View Web application developmentSee the walkthrough: Customer portal walkthrough
If visitors cannot understand what you do or take the next step, start with the journey. Website design, a manageable CMS or a careful redesign each solve a different part of that problem.
View Websites & platformsRead the guide: When should you redesign your website?
Development and operational support for agencies that need additional capability, with the communication boundary and the handover agreed before delivery begins.
View the page for agenciesRead the guide: Mobile app handover checklist
AI automation, custom web applications and customer portals lead our work. Websites, commerce, mobile apps, search and hosting complete the plan when the product needs them. These are the platforms and tools we work with.
Connect intelligent tools with everyday operations.
Create assistants for defined business tasks.
Move the right information between your teams and tools.
Find failures early and manage changes to running workflows.
Bring workflows, permissions and data into one product.
Documents, updates, requests and account details in one place.
iOS, Android and cross-platform apps for customers and teams.
Bring your business to the web.
Help visitors find the right service and get in touch.
A CMS built around the people who edit your website.
Redesign or move a site with content and URLs planned together.
Updates, fixes and planned improvements after launch.
Review points are agreed before the work gathers momentum, so the business goal stays connected to the design, the delivery and the care of the finished product. Four stages, each closed by a review.
A brief, priorities and delivery scope.
Gates: Problem and decision-maker agreed
Experience designs and a working build.
Gates: Journeys and connections reviewed
A release checklist, acceptance checks and handover.
Gates: Readiness and operation confirmed
Measurement, support needs and a prioritized backlog.
Gates: Next phase agreed
We discuss what belongs in the first phase, who approves business facts, which existing platforms remain and which external costs or provider decisions affect delivery. You can also commission a narrower piece of work when that is the responsible next step.
Prices, support coverage and outcomes are agreed in a proposal rather than assumed from a service list.
The engagement models, what drives cost and what a proposal contains.
View how pricing worksThe model follows the work. Each one is priced on its own basis, and the amounts are set in your written proposal.
| What to compare | Project deliveryView Project delivery | Ongoing supportView Ongoing support & development | Dedicated teamView Dedicated delivery team | Agency deliveryView the page for agencies |
|---|---|---|---|---|
| Fits when | The outcome can be defined now | A live service needs care and planned improvement | A continuing roadmap needs reserved capacity | An agency needs delivery support for its client |
| Scope is set by | Agreed deliverables and acceptance checks | A shared priority order within agreed coverage | A product owner who orders the backlog | The agency’s brief and its client relationship |
| Priced on | The agreed scope, with payment milestones | Agreed capacity and coverage | Capacity, duration and notice terms | A defined project or continuing work |
| Changes | Assessed and approved before they join the project | Prioritized in the shared queue; larger changes get their own scope | Reviewed with the product owner as the roadmap moves | Evaluated by both teams before anyone promises a new outcome |
Hosting, subscriptions and usage-based services such as AI providers may be billed separately; your proposal lists the ones that apply.
Choose this when the result can be defined before work starts.
Choose this to keep a live product healthy and improving.
Choose this when the roadmap keeps changing and needs steady capacity.
Choose this when the work belongs to your agency’s client relationship.
Reliability, portal cost and the choice of workflow tool are the questions that move an estimate most.
Explicit state, duplicate handling, bounded retries and a human route for uncertain outcomes.
Read the guide: Keeping business automations reliableCount the workflows, access rules and integrations before counting screens.
Read the guide: Customer portal development costCompare the tools on your own workflow, its connectors, governance and who will operate it.
Read the guide: n8n vs Make vs Zapier for your workflowA current URL, a customer question, a broken workflow or a description of your stack is enough to start. We can identify the missing information together.
A current URL or the product you run
The customer question or task that goes wrong
The workflow that breaks, and where
A description of your stack and the systems it connects
Do not send credentials or confidential customer records through a first enquiry.
The goal of the conversation is a sensible next decision: investigate, improve what exists, or define a new build with clear ownership.
Some of the teams we have worked with.
Across talent, fitness, mobility, payments and local commerce.No. We recommend the smallest useful scope based on the problem. If design, development, marketing or hosting depend on each other, we make those dependencies visible, but each proposed deliverable and responsibility is agreed before work begins.
That is often the first option to assess. We review the current platform, access, constraints and operating costs before suggesting extension or replacement. A new tool is not automatically better than a well-scoped improvement to the existing one.
Small and mid-sized businesses and agencies. We design and build websites, custom web and mobile apps, and AI-enabled automation, with agreed review points and a documented handover.
Your first conversation is with Gary C., our client partner. The people who design and build your project are agreed with you during scoping, so you know who is responsible before work begins.
Describe what people struggle to do today and the systems involved. We can separate automation, software, website and operating work, and propose the smallest useful scope.
Technology names and marks belong to their owners.
