Updated
Actors may receive audition details on several casting sites while managing deadlines, callbacks and bookings elsewhere. A tracking product needs dependable data entry and a clear record of what happens next. Another dashboard is less useful if the actor still has to copy every detail by hand.
Curiosive's Auditional case combines a web application with Chrome, Safari and Firefox extensions that import auditions from Actors Access and Casting Networks. We use that delivered workflow to help US product teams scope connected tools for actors. It is not evidence of building those casting platforms themselves.
Define the journey from receiving an audition to recording a callback or booking. List the fields that matter, the deadlines users act on and the difference between imported and manually entered records. Agree how duplicate imports, incomplete details and corrections should behave. The first release should support a complete actor task instead of a broad set of charts with unreliable underlying records.
Auditional's published scope is an audition tracking and management platform with one-click casting-site import through Chrome, Safari and Firefox extensions. The web application tracks status and deadlines and presents insights on auditions, callbacks and bookings. Svelte, TypeScript, Firebase and Tailwind CSS form its stack. Those are implementation examples, not a promise of bookings, automated casting decisions or a result for another product.
A browser importer reads an interface that another company controls. Agree the supported sites, fields and browsers, what access the extension needs and what happens when import fails. Confirm the authorized integration approach and any platform restrictions with the responsible team before implementation. Include representative examples and a maintenance owner in the scope; a working sample is not proof that every page variation will work.
For a new audition tracking product, show the source reference and the extracted fields that will become the record. Decide which missing or ambiguous values need actor review, including deadlines whose source does not state a time zone. Keep the supplied value visible rather than silently inventing one. Compare one complete example, one incomplete example and an audition already entered manually. Agree which fields an import can update and which actor edits it must preserve. Auditional provides evidence of connected import and manual tracking; preview, time-zone and merge rules must be accepted for your own supported workflow.
The extension and web app should share a clear account and record model. Specify who can read or change an audition, how a user corrects imported details and how errors surface without losing work. Define the first supported import path and its acceptance examples, then expand to another browser or source after review. Exports, retention and third-party integrations need explicit decisions rather than assumptions hidden in the interface.
For a new tracker replacing a spreadsheet or another tool, review an authorized sample export before moving live history. Map each record to its actor, audition reference, recorded status and notes. If the old export contains only the latest status, preserve that limit instead of inventing earlier status changes. Compare an active callback with a closed audition and reconcile unmapped or deliberately excluded rows before cutover. Agree when the old tracker stops accepting edits and which system becomes the working record. Rehearse that transfer separately from importing a new audition through the browser. Auditional establishes connected import, manual entry and tracking; historical data conversion and the cutover process would be separately scoped work.
For a new engagement, bring authorized sample source pages, the fields to import and the deadline and status rules actors use. Decide how an imported record relates to a manual one. Proposed acceptance examples: importing the same audition twice follows the agreed duplicate rule; missing fields produce a recoverable review step; an actor can correct a record without losing its status history; and each named browser completes the supported import-to-dashboard task. Assign the owner for a changed host page. These are proposed checks for a new build, not retrospective claims about Auditional's tests.
Curiosive LLC is a US company; engineering is led from Ankara, Türkiye. We agree a written scope, capacity, review windows and release responsibilities before work starts. Monthly AI-accelerated development starts from $2,000. Bring the existing system, the person who owns the workflow and examples of a successful task. A bounded first increment is easier to review than a replacement of every tool at once.
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.
The Auditional example demonstrates actor tracking and casting-site import, not a casting marketplace. A marketplace needs its own role model, submission workflows and commercial scope before an estimate.
Supported sites and browsers must be agreed and tested. Third-party interfaces and access conditions can change; maintenance and failure handling belong in the engagement scope.
Auditional's published scope includes manual entry alongside import. For a new product, agree the manual workflow and how it interacts with imported records and duplicate detection.
Choose one authorized source, the fields to capture and representative complete, incomplete and previously entered examples. Agree how the actor reviews uncertain deadlines and how a repeated import treats manual corrections. Accept that record-to-dashboard task before expanding to another source or browser. These are proposed scope decisions, not claims that Auditional used a particular review or merge policy.
Representative authorized audition examples, target sites and browsers, account roles, the required status history and a description of how users currently track deadlines. Avoid including real personal data when sample records are enough.
Treat collaboration as a separate proposed role, not an assumption about Auditional. Agree who can invite someone, which audition details they may view or edit and which notes remain actor-only. Include an uninvited second actor and a removed collaborator in the proposed access checks. The published case establishes actor tracking and browser import; it does not establish these invitation, sharing or revocation rules.
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