WORKING WITH ONIXUS
Know what happens next.
A defined package, a written scope and a delivery contact. Start with what your business needs to build, grow or automate.
A clear path from your first question to delivery.
01
Choose your outcome
Start with Build, Grow or Automate. Tell us what you need, what you already have and your budget.
02
Agree the details
Review deliverables, price, timing, revisions and required accounts. Paid work starts with an agreed written scope before purchase.
03
Prepare for delivery
Complete onboarding, share the required assets and agree review points. Confirm launch, handoff and ongoing support for your service.
Need a person to help you choose? Contact the Onixus team or book a discovery call.
Before payment
Your proposal records the selected package, deliverables, quantity, revisions, dates and responsible delivery contact. Review account access, ownership, hosting and third-party charges before accepting. Your scope request does not start a subscription or take payment.
When the clock starts
Delivery targets start after the approved brief, required assets, account access and agreed payment are complete. We confirm your start date before work begins. Missing inputs or delayed feedback move the schedule; extra work needs a separate agreement.
Review and changes
Use one contact to consolidate feedback. Each package lists its included revision rounds. Corrections of Onixus errors do not consume a revision round. New features, additional assets or a new creative direction require an approved change to scope and price.
Monthly services and renewal
Confirm your service start date, billing amount and next renewal in writing. Monthly services are billed in advance on the agreed schedule. Request cancellation before the next renewal to stop the next charge; the team confirms the effective date. Unused work does not roll over unless agreed in writing.
If something goes wrong
Contact the team with the affected service and what happened. We review the issue, communicate a recovery plan and agree the next update. Undelivered work needs an appropriate remedy; a queued post is not a published post. Response coverage and escalation arrangements are recorded in your proposal.
At handoff
Review the work against the agreed scope. Receive the agreed files, access and instructions, with customer-owned accounts and third-party licenses clearly identified. Website packages include 14 days of scope-related defect corrections after launch; ongoing maintenance and new features are separate.
Our approach to improving a workflow
1. Question every requirement
Before scoping a feature, client ask, or internal process, challenge whether it needs to exist at all.
2. Delete before you build
Remove unnecessary steps, tools, approval layers, and scope before adding automation or new code.
3. Simplify what survives
Only after deletion, reduce the remaining process to its leanest working form.
4. Accelerate cycle time
Speed up build, negotiation, and delivery loops.
5. Automate last
Only automate a process once it has been questioned, cut, simplified, and sped up.