Choosing a route
Customised or bespoke: choosing your game route
Choose an existing game when a specific available title fits your needs. Customise an authorised foundation when its supported gameplay suits the brief and you want a new identity. Choose bespoke development when the experience requires an original structure or substantial gameplay changes. Availability, rights and technical fit must be confirmed for each route.
An existing game: review the actual package
Start with an identifiable title and a conversation about its availability. Ask what build, files, rights and support are supplied, and whether your intended market and platform are covered by the proposed arrangement.
A public portfolio demonstrates a studio’s work. It does not automatically make that studio’s code, characters or themes available for purchase or reuse. PlayBeSpoke’s game portfolio and its concept studies serve different purposes.
A foundation: retain a suitable structure
A foundation route begins with a reusable structure whose permissions and capabilities have been confirmed. Your commission can define a new world, character, symbols, interface treatment and promotional assets around the supported game.
Make a list of what remains unchanged and what needs adaptation. If the request changes mechanics, game states or the maths, the team must assess the impact. A visual reskin is not evidence that every requested gameplay change is supported.
- Does the existing gameplay fit the brief?
- What artwork and interface treatment will change?
- Are the proposed feature changes supported?
- Which files and reuse rights are included?
Bespoke: define an original experience
Bespoke development begins with a brief and a shared blueprint. The team works through the core experience, visual language, maths responsibilities, technical requirements and production stages before agreeing the build.
This route gives room for an original concept, but the project still needs defined boundaries. Confirm the required features and supported devices, then use review stages to resolve decisions. Changes after approval are assessed for their effect on work, price and timing.
Use your requirements to make the decision
Bring your non-negotiables to the first conversation: the gameplay idea, brand treatment, platform, intended markets, source-file needs and desired launch window. Add what you already own and what your team can supply.
We can then discuss whether a specific existing solution, an authorised foundation or original development fits. The recommended route should explain the work it covers and the assumptions it relies on. You can commission a defined part of production without becoming a studio partner.
- List must-have features and flexible preferences
- Identify supplied assets and permissions
- Confirm integration and approval responsibilities
- Compare proposals against the same output
Put it into practice.
Use these editable planning resources with your team. They are examples, not a quote, certified model or committed delivery scope.
Download the production handover register ↓Download a fictional slot brief example ↓Existing game solutions ↗Customise a foundation ↗Commission a bespoke game ↗Your project. One shared space.
Shape your idea in Creator, review the visuals and agree the next step in your private client studio.