An employee learning a workplace tool often needs a short explanation beside the task they are trying to complete. That guidance also needs an owner, an intended audience and a plan for when the underlying tool changes. We help Ann Arbor, Michigan teams develop video onboarding software around approved workplace journeys.
Our Reveal Software work, recorded in Romania, connects a web application, in-product video extension and administration for users, roles and activity. It provides relevant multi-surface delivery evidence for a separately scoped employee tool. Curiosive uses AI to accelerate implementation with engineer review and stays involved as a long-term product partner as content and workplace tools evolve.
Start with one approved tool and a task new employees regularly need to understand. Define the page context, the explanation and the point where the person returns to work. A role may need a different guide or no guide at all. Agree how the employee finds help again after dismissing it. Keeping the first scope tied to a representative task gives the team a concrete way to review the video, interface and access model together.
The Reveal case describes a monorepo with a Next.js web application, a browser extension that overlays video walkthroughs inside another product and an administration dashboard for users, roles and activity. React, TypeScript, Hono, Drizzle ORM and PostgreSQL support the product. The project is recorded in Romania and concerns personal video onboarding for SaaS. Its connected web, browser and backend delivery provides a reference; employee-specific audiences, editor approvals and workplace integrations would be defined in a new Ann Arbor engagement.
Define who can publish or retire a guide and which employee roles can open it. Agree the information that connects a walkthrough to its supported workplace page. A revised procedure may require a new video and a deliberate replacement rule. If the product stores activity, define the actual event and its permitted audience rather than treating a playback signal as proof that someone understands a task. Keep the approved purpose and data behavior clear in the product scope.
The workplace page can change its layout or remove the target a walkthrough expects. Decide whether the guide remains available in a separate panel, shows an updated explanation or follows another agreed fallback. Review keyboard access, dismissal, a narrower window and an unavailable video against the supported task. AI accelerates component exploration and familiar integration work; engineers review permissions, content relationships and recovery. Your team approves the guide content and the workplace tools the extension is allowed to support.
For a new engagement, bring approved videos, representative workplace pages and the intended employee and editor roles. Proposed acceptance examples: an eligible employee opens the matching guide in a supported tool; a different role follows the agreed access rule; dismissal returns to the intended task; and a retired guide follows its approved replacement behavior. Include a changed host page and an unavailable video. These are proposed employee-tool checks, not claims about Reveal's historical HR delivery, employee monitoring or onboarding outcomes.
Employee questions and content-owner updates reveal where guidance needs a clearer explanation, a different trigger or a better return path. We collaborate through a shared backlog and reviewed releases so the library and integration develop together. Monthly AI-accelerated development starts from $2,000, with capacity, approved tool contexts and operating responsibilities agreed in writing. Curiosive LLC works remotely with Ann Arbor teams through agreed Eastern-time review windows, with engineering led from Ankara. The relationship continues beyond the first onboarding video rollout.
Senior engineers building your product with AI coding agents: web, mobile, SaaS or browser extension, reviewed before anything ships.
AI-accelerated development, billed monthly. We confirm scope, capacity and start date in writing before checkout.
Yes. Bring approved walkthrough content, representative workplace pages and the intended roles so we can scope a focused guidance tool.
Its Romania-recorded case demonstrates connected web, video overlay and administration surfaces for SaaS onboarding. Employee-specific policies would be new requirements.
That can be an agreed requirement. Define the role mapping, guide ownership and access checks for the supported workplace contexts.
Yes. A continuing engagement can prioritize host-page changes, content revisions and employee feedback through a shared backlog and reviewed releases.
One paragraph on what you are building, roughly when you need it, and who it is for. No brief, no form with fifteen fields.
From the engineer who would do the work, not a sales team. If we are not the right fit we say so, and where possible we point you somewhere better.
Scope, price and timeline in writing before anything is committed. You decide with the numbers in front of you.
No long contract to begin, no lock-in to our tooling, and the code is yours from the first commit.
Start a conversationA short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.
Ankara / Türkiye · Working across European and US time zones