01 — Digital web practice
We decide what your site should do, design how it looks and behaves, build the front end, and prove it performs and stays usable. You keep every file.
02 — Services
Six services covering the route from an unclear online strategy to a built, tested front end. Open any service to see the full scope and place an order from the same panel.
Prices are United States dollars and reflect a typical starting scope. A firm quote follows your order, and no work begins before scope, schedule and fee are agreed in writing.
Not sure which one03 — Process
Every engagement runs through the same four stages. Each one closes with something concrete to review and approve, so you always know what has been decided and what is waiting on you.
We start from the business, not the layout. What the site is for, who it serves, what it currently fails to do, and which constraints are fixed. An existing site is audited before anything is proposed.
OutputWritten brief with agreed goals and scope
Navigation, hierarchy and content model are settled first, then visual direction is agreed against them. Structure is approved before appearance is discussed, which keeps later revisions small.
OutputWireframes and an approved visual direction
Interface design is completed as a system, then the front end is built from it. Feedback is collected in rounds rather than continuously, so each revision is judged against the whole.
OutputDesign files and working front-end code
The build is tested across browsers and devices, checked for performance and reviewed against accessibility guidance. Files are organised, code commented, and handover notes explain how to extend it.
OutputTested code, organised files, handover notes
Work is carried out remotely. Design files are produced in Figma, with Canva-ready exports where a marketing team needs to reuse assets, and front-end code is delivered in a form your own developers can pick up without a rewrite.
04 — Deliverables
Every engagement ends with material handed over in an editable, standard format. Nothing is locked to a tool you cannot access, and nothing depends on us remaining involved after the project closes.
Written decisions rather than presentation slides, in a format you can circulate internally and act on without us in the room.
FormatPDF and editable document
A working design system with components, states and a documented type and colour scale, not a flat set of exported images.
FormatFigma source, Canva-ready exports
Readable, commented front-end code structured so another developer can extend it without unpicking how it was written.
FormatCommented source files
05 — Approach
Orivanta Sphere is a small remote practice. That shapes how we take work on: fewer projects, direct contact with the person doing the work, and a written record behind every decision.
Navigation, hierarchy and content are settled before visual design begins. A site that looks considered but buries the thing visitors came for has failed at the stage that mattered, and no amount of styling recovers it later.
Scope, schedule and fees are agreed in writing before work starts, and every stage closes with something concrete to approve. If a request falls outside the agreed scope, we say so and quote it rather than absorbing it quietly and slipping the schedule.
Semantic structure, keyboard operation, focus states and colour contrast are handled during the build, not retrofitted after a complaint. Building this way costs little at the time and is expensive to add once the front end is finished.
Front-end work is written to be inherited. Clear structure, meaningful names and comments where intent is not obvious, so your own developers or your next supplier can extend the work rather than starting again.
Performance and accessibility claims are backed by measurement taken before and after the work. Where a change cannot be evidenced, we describe it as a judgement rather than presenting it as a result.
06 — Reviews
Written feedback from founders, marketing leads and in-house developers on consulting engagements, interface design, front-end builds and audit work.
07 — Start a project
Send a short brief and you will receive a written reply within one business day covering scope, a realistic schedule and a firm fee. If the work is not a fit for this practice, we say so rather than quoting for it.
All fields must be completed before the message can be sent.
All fields are required. We reply within one business day.
Your project details have been logged with the Orivanta Sphere studio. A written reply covering scope, schedule and a firm fee will reach you within one business day, sent from projects@orivantasphereonline.com. If anything needs clarifying first, that reply lists the specific questions rather than a general request for more detail.
Your referenceOS-000000
