It can deliver the cue-and-table experience plus rules, modes, multiplayer, backend, admin, QA and release systems defined in the product scope.

Yes. A new engagement can begin with discovery and a playable shot prototype before the complete scope and production plan are approved.

Custom development starts with the intended audience, rules, modes, brand, art direction, platforms and business model. Capermint then designs original game UI, shot behavior, progression, multiplayer, backend and operations around that product brief rather than applying a generic reskin.

Yes. A turnkey scope can cover discovery, UI/UX, original art, gameplay physics, mobile clients, authoritative multiplayer, backend, admin, QA, store preparation, deployment, handover and post-launch support. Exact inclusions, dependencies and acceptance gates are listed before production.

A white-label-ready route can be assessed when an appropriate reusable foundation exists and its rights are clear. Scope may include branding, UI, rules, modes, backend configuration and launch customization. Otherwise Capermint will recommend a custom build rather than misrepresenting a template as a finished product.

Capermint can build an original cue-sports product with familiar category mechanics, but it should not copy another publisher's protected code, brand, art, interface, data or trade dress. The product brief defines an original visual identity, progression model and implementation.

Yes, subject to prototype and browser-matrix findings. An HTML5 or WebGL client can support pointer and touch input, shared identity and online matches while loading, lifecycle, performance and hosting constraints are validated for the target browsers.

Yes. A casual product can use shorter sessions, clearer assists, faster onboarding and lighter progression. A hyper-casual direction needs an even narrower loop and distribution plan. Neither label replaces testing the shot feel, audience and retention premise.

Yes. The team can assess the document, expose missing decisions and convert it into prioritized systems, milestones and acceptance criteria.

Common options include practice, quick 1v1, friend rooms, ranked seasons, tournaments and club events. The final mix is selected around audience and operational capacity.

Yes. Original tables, cues, UI, animation, VFX, audio and broader art direction can be created or integrated from approved client assets.

Potentially. Shared identity, progression and match services can support multiple clients when platform constraints and simulation strategy are resolved during architecture.

Yes, subject to an audit of repositories, builds, dependencies, infrastructure, accounts, documentation and known defects before ownership expands.

Either may be appropriate. A clickable flow proves navigation; a playable prototype is preferred for shot feel, physics and multiplayer risk.

The team defines an accepted model for input, force, friction, collisions, cushions, spin and pockets, then validates it with repeatable golden-shot scenarios.

Yes, when advanced spin is in scope. Its control, transfer and post-contact behavior are prototyped and tested as part of the shot model.

Yes. The approved rules can align to a WPA reference while remaining an independent product implementation with no implied affiliation or certification.

Yes. Custom break, timer, foul, aim or event rules are documented as product variants and given their own acceptance scenarios.

Yes. Guide length, bounce preview and assistance can be mode- or progression-aware when the policy is clear and consistently enforced.

A practice bot or AI opponent can be scoped around shot selection, difficulty, thinking time and target device constraints.

Representative jaw, shelf, speed and approach-angle cases are replayed against signed-off tolerances to prevent visibly contradictory results.

The answer depends on the architecture. The prototype determines where simulation is authoritative and what replay tolerance is acceptable across platforms.

Yes. Scope can include matchmaking, rooms, turn authority, shot validation, state sync, results, rematches and reconnect behavior.

It is the trusted service that validates important commands and resolves match state or results instead of accepting every client claim.

Matchmaking inputs can include region, latency, queue time, mode and a selected skill model. The exact policy is tuned and observed after launch.

The product defines grace periods, state recovery, retry limits and safe match outcomes, then tests them under backgrounding, network changes and packet loss.

Yes. Typical layers include command validation, impossible-action checks, authoritative results, rate limits, audit logs and escalation tooling.

Yes. Private codes, deep links, invites, presence, rematches and optional spectators or chat can be included.

Yes. The format, scheduling, tie logic, ranking, reset cadence, moderation and operational controls must be selected in scope.

The release can include logs, metrics, alerts, dashboards and a runbook for the selected services and support model.

The agreed console may cover players, configuration, content, progression, matchmaking, moderation, events, support diagnostics and audit history.

Selected rules, content and economy values can use versioned remote configuration with permissions, validation and rollback controls.

The schema is defined around decisions such as onboarding, match health, shot behavior, progression, content and technical reliability—not raw event volume.

Yes. The moderation approach can include filters, reports, mutes, sanctions, audit logs and human review based on the product’s audience and regions.

Yes. Event configuration, start and end times, missions, rewards, messaging and fallback behavior can be administered when included in scope.

No. This page describes an entertainment product. Cash-prize, wagering, deposit and withdrawal systems are outside Capermint's service scope for this product.

A non-withdrawable virtual currency or cosmetic entitlement system can be designed with clear sources, sinks, disclosures and platform-policy review.

Yes. Language, text expansion, input, color, motion, readable feedback and assistive requirements are planned against the selected platforms and audience.

Security scope can include trusted server decisions, authentication and authorization, role-based admin access, secret management, encrypted transport, rate limits, command validation, dependency review, logs and incident runbooks. Exact controls follow the architecture and risk assessment.

The product maps collected data, retention, consent, age considerations, SDK disclosures and store requirements for its selected audience and regions. Legal determinations remain with qualified counsel; the implementation and release evidence follow the approved requirements.

A responsible estimate follows discovery of modes, physics depth, multiplayer, content, operations, platforms and inherited risk. Capermint does not present a fake fixed price without that scope.

The timeline depends on mode count, shot-physics depth, multiplayer and backend scope, original content, target platforms, integrations, compliance and inherited risk. A prototype can answer critical questions before a milestone plan and target release window are committed.

A team may include product, game design, gameplay and backend engineering, art, UI/UX, animation, QA, DevOps and production roles according to scope.

Yes. A dedicated or co-development team can provide gameplay, Unity, backend, art, UI/UX, QA or LiveOps capacity around defined ownership, cadence, backlog and integration responsibilities.

Ownership, assignment, pre-existing materials and third-party licenses are defined in the contract. Handover follows those agreed terms.

They can be explicit deliverables, including architecture, rules, configuration, build, release, known issues and operational runbooks.

Yes. Options can include warranty, maintenance, monitoring, balancing, content, events and a longer LiveOps cadence with agreed service boundaries.

Yes. Capermint can structure B2B delivery for a funded startup, established publisher, agency, brand or enterprise team through a turnkey build, co-development boundary, dedicated specialists or an audit-first takeover.

NDA terms can be agreed before sensitive product materials or system access are shared. Service levels for monitoring, support, response and maintenance depend on the post-launch engagement and are documented in the applicable contract rather than assumed from the build scope.

Share the audience, platforms, mode mix, current assets, desired launch window and major constraints. Capermint can then recommend discovery, a prototype or an audit-first takeover.