How to evaluate Oviompt before you hire
A website can explain an approach. Before you commit money or access, ask for the evidence and terms that matter to your project.
What you can inspect now
- Published planning ranges for products and focused services.
- The delivery method, from scoping to handover.
- An illustrative decision record with trade-offs and acceptance tests.
- Editorial standards for our technical writing.
- Website privacy and contact-data handling.
What to confirm before signing
Ask for the contracting legal entity, jurisdiction, named delivery team, scope, exclusions, milestone dates, acceptance criteria, ownership terms and support responsibilities in writing. Confirm these before making a payment or granting access.
Legal registration details, team identities and independently verified certifications are not published on this website. Request the relevant documentation for your diligence; do not infer it from our branding or technical articles.
References and project evidence
The work register is private. Ask whether a relevant client-approved reference or redacted deliverable is available for your proposed engagement. Availability depends on the client’s permission. The public sample is explicitly illustrative and should not be treated as client evidence.
Start with a bounded engagement
An audit is a possible first step: the published planning range is $3k–$10k over 1–2 weeks. Agree the questions, evidence to inspect and written deliverable before starting. Review the full pricing table for other engagement shapes.
Payment, ownership and termination
The existing engagement model uses 50% on signature and 50% on delivery below $25k; 33%, 33% and 34% at agreed milestones from $25k to $120k; and milestone payments above $120k. The signed proposal must confirm the applicable schedule, currency, taxes and deliverables.
Request the cancellation, delayed-delivery, source-code ownership and post-handover support clauses before signing. A marketing page does not replace the agreement. If insurance or certification is required, ask for current documentation and verify its scope.
Security and project data
Start with a non-confidential brief. Before transferring sensitive data, agree access controls, hosting, retention, subprocessors and any required NDA or data-processing terms. The intended delivery model keeps project artifacts in the buyer’s chosen repository and infrastructure, with scoped access.
Report a website vulnerability to security@oviompt.com. See the security contact file for the disclosure contact.
Questions before a proposal?
Email hello@oviompt.com with the evidence or contract questions you need answered. You can also send a short project brief. No mandatory discovery call.