Seen on top review platforms
OTYS is your ATS (applicant tracking system), software that stores your vacancies, candidates, and stages. If your website disagrees with it, you get ghost jobs, wrong filters, and applicants lost in redirects.
That costs you trust, and time.

Some facts
OTYS data surfaces usually matter, the vacancy feed and the application intake.
records need clean IDs early, vacancy, candidate, application, client, contact.
ownership rule prevents chaos, decide where every field is edited.
If you’re migrating from Bullhorn, Recruitee, Teamtailor, or Cockpit into OTYS, we plan the cutover and keep your careers site stable. Tell us what needs to sync, and what must never break.
We’ve been building and maintaining digital products long enough to know what breaks, what scales, and what “urgent” actually means.
Studio Ubique works with startups, agencies, and mid-sized companies who want their product to work better than their competitors’ excuses. Since 2012, with clients across 15+ countries.
The questions that come up most often, answered here. Yours not among them? Just ask, there's a human on the other end.
Depends on scope. Standard OTYS vacancy feed integration with filters and search on an existing WordPress site: €8.000 to €15.000. Full OTYS integration with vacancy feed, application intake with writeback to OTYS, candidate dedupe, and admin health dashboard: €15.000 to €30.000. Complex setups with custom portals (candidate portal, client portal), SSO, multi-language, or migration from another ATS into OTYS: €25.000 to €50.000+. Hourly rates run €60 to €65 across engineering, integration, and project management. Add-on work after launch (new fields, additional filters, reporting changes) typically scoped as small sprints or rolled into ongoing support. Our pricing page covers the broader rate structure.
Typical timelines. Standard vacancy feed integration on existing site: 3 to 5 weeks from kickoff to live. Full OTYS integration with application intake plus writeback: 6 to 10 weeks. Complex setups with portals, SSO, or ATS migration: 10 to 18 weeks. The variable that surprises clients: data mapping discovery takes longer than coding. OTYS fields versus your website fields rarely match one-to-one, and the mapping document is where edge cases surface (what counts as “open” status, how location aliases work, what happens to expired vacancies). We typically spend 1 to 2 weeks on mapping discovery before any sync code gets written. Our process page covers the project structure.
Standard ATS migration approach. First, parallel data audit: what lives in your current ATS, what needs to move to OTYS, what gets archived rather than migrated. Second, OTYS data model setup: configure custom fields, categories, statuses to match the data structure coming in. Third, historical data migration if needed (candidates, applications, notes, attachments) via OTYS import or manual entry depending on volume. Fourth, careers site re-integration: rebuild or adapt the vacancy feed and application intake to talk to OTYS instead of the old ATS. Fifth, parallel running period (1 to 2 weeks) where both systems stay live to catch any data gaps. Sixth, switchover and decommission. Critical concern: keep the careers site stable throughout. Visitors should not see a “site under maintenance” message during the migration, and recruiters should never lose access to candidate data. Migration timelines depend on data volume and how complex the source ATS configuration was.
Depends on what else the site needs to do. WordPress with OTYS integration fits well when: editorial content (blogs, employer branding, case studies) matters alongside the vacancies, your content team is comfortable with WordPress, the budget is constrained, and the vacancy display can use standard list and detail patterns. Typical WordPress plus OTYS integration projects sit in the €10.000 to €25.000 range. Custom CMS with OTYS fits well when: the careers site has unusual UI requirements (custom matching algorithms, candidate dashboards, complex multi-step apply flows), the parent organisation already runs on a non-WordPress stack (Next.js, custom Laravel, headless), or content workflows are too specific for WordPress to handle cleanly. Custom CMS projects with OTYS integration typically run €25.000 to €50.000+. Most clients with standard recruitment site needs land on WordPress with OTYS integration. Custom CMS is right for clients with genuine UI complexity or existing technical stack constraints.
A well-built OTYS integration should degrade gracefully, not break. Standard approach: cached vacancy data on the website side (typically 5 to 15 minute cache), so OTYS API downtime under that window is invisible to visitors. If OTYS is down longer, the site continues serving the most recent cached vacancy list with a small “data last updated X minutes ago” indicator. Application submissions during OTYS downtime get queued client-side or server-side, then submitted when OTYS comes back. Retries happen automatically with exponential backoff. Failed submissions trigger alerts to the operations team, plus a visible status indicator for recruiters so they know which applications are pending writeback. The runbook we deliver at handover documents exactly what to check and how to clear queued submissions in case of extended OTYS downtime. The careers site should never show “error 500” or a blank vacancy list because of OTYS issues.
Standard post-launch package includes 30 days of monitoring and bug fixes after go-live. During this window: daily check of sync logs, weekly review of any failed applications or sync errors, immediate response to broken integrations during business hours. After 30 days, ongoing support moves into one of the Care, Growth, or Partnership packages. OTYS changes its API occasionally (field additions, deprecations, authentication updates), and the integration needs maintenance to stay current. Most clients with active recruitment operations choose Growth or Partnership for ongoing OTYS work, since hiring teams notice immediately when something breaks (recruiters can’t post a vacancy, applications stop arriving). For organisations with infrequent hiring activity, Care tier with quarterly review cycles is usually enough. New features (additional fields, new filters, custom reports) are scoped as separate sprints outside the support package.
Book a quick 30 min video call, we will show you exactly what to fix. We reply within 24 hours.