# Buy a useful RPG vertical slice before a larger build
Source page: https://dfygames.com/guides/rpg-vertical-slice (published 2026-10-19, updated 2026-10-19) · Topic: Hero battler RPG games
Cite as: DFY Games, "Buy a useful RPG vertical slice before a larger build", updated 2026-10-19, https://dfygames.com/guides/rpg-vertical-slice

**Quick answer:** A useful RPG vertical slice is a thin piece of the game at final quality: one complete battle loop, one full progression step and just enough content to repeat it, with everything else deferred. Agree the battle, progression and content matrix and written acceptance criteria before work starts, so you can judge the slice on facts before committing a larger budget.

- Slice contains: One battle loop, one progression step
- Quality bar: Final quality, thin content
- DFY route: Advanced first playable, day 10
- Decide before: Committing the full build budget

## What a vertical slice is for

A vertical slice cuts through every layer of the game (input, battle rules, UI, art, sound, progression) for a small amount of content. A horizontal prototype does the opposite: every system in rough form, nothing finished. RPG buyers usually need the vertical kind, because the questions that decide an RPG budget are about feel and pacing. Is a battle satisfying? Does the first upgrade make the hero noticeably stronger? A rough prototype cannot answer those.

Decide what the slice is for before you scope it. A slice for your own go or no-go decision should prove fun and pacing. A slice for investors or a publisher also needs presentation polish. A slice for testing ad creatives needs the moments that make good clips, such as the ultimate skill and the victory screen. Each purpose changes what goes in.

## What a vertical slice delivers, and what it does not

Most disappointment with a slice comes from expecting it to be a small finished game. Agree the two lists below before work starts, so both sides judge the same thing.

Deliverable in a vertical slice:
- [ ] An installable build for iOS and Android test devices
- [ ] One complete battle loop at final art, sound and UI quality
- [ ] One full progression step: loot, upgrade and a visibly stronger hero
- [ ] A small, named content set, such as one chapter and one boss
- [ ] Local save for the content in the slice
- [ ] Build notes listing known bugs, placeholders and every deferred item

What a slice does not include, even when it passes every acceptance check:

- Not a store release. The slice is a checkpoint build for you and your testers; submission comes with the full build.
- Not the full roster, map or story. Anything in the deferred column is absent by design.
- Not a finished economy. Prices are placeholders and the purchase catalogue is not built.
- Not online features. Accounts, cloud save, guilds and player-versus-player are outside the slice.
- Not evidence of retention or revenue. A slice shows feel and pacing to a handful of testers; store data only comes after launch.

## The battle, progression and content matrix

Fill in this matrix with the developer before work starts. The middle column is what you are buying now. The deferred column is just as important, because it stops the slice from slowly turning into the full game.

| Layer | In the slice | Deferred to the full build | Acceptance test |
| --- | --- | --- | --- |
| Battle rules | Turn order, basic attack, two skills and one ultimate per hero, one status effect, win and lose states | Additional status effects, elemental counters, auto-battle, speed-up | Ten battles in a row finish with a win or loss screen and no stuck states |
| Enemy behavior | Two regular enemy types and one boss with a telegraphed big attack | Full enemy roster, elite variants, further bosses | The boss's big attack is announced a turn ahead and a first-time player can react to it |
| Heroes | Three playable heroes at final art quality | The rest of the roster, rarity tiers | Each hero's role (damage, defense, support) is clear to a new player after one battle |
| Progression | One full step: win, receive loot, level up or equip gear, become measurably stronger | Skill trees, rune fusion, gear sets, prestige | A lost battle can be won after one upgrade, with the stat change visible on the hero screen |
| Content | Three or four stages on one map chapter, ending in the boss | Further chapters, side stages, daily content | A new player finishes the chapter in one sitting without your help |
| Economy and monetization | One soft currency, one rewarded ad for extra loot, prices shown as placeholders | Full in-app purchase economy, offers, battle pass | The rewarded ad flow works end to end with test ads |
| UI and screens | Battle, victory, hero detail and chapter map | Roster, shop, settings beyond the basics, events | Damage numbers and buttons readable on the smallest supported phone |
| Save and stability | Local save of hero levels and stage progress | Cloud save, account linking | Progress survives closing the app from the task switcher |

![Hero detail screen: a frost oracle framed by a glowing rune circle, with six gear slots, attack, defense, health and speed stats, skills and a Level Up button](https://dfygames.com/media/games/rune-legends/detail.webp)

## Acceptance criteria to agree in writing

Acceptance criteria turn "I'll know it when I see it" into checks both sides agree on. Write them before work starts and keep them observable: something you can do on a phone and see happen. The matrix column above covers the systems; the list below covers the slice as a whole.

Slice acceptance criteria:
- [ ] Installs and runs on the agreed test devices for iOS and Android, including the oldest supported phone.
- [ ] A first-time player completes the opening battle without instructions from you, and sees the ultimate skill within it.
- [ ] The full loop (battle, loot, upgrade, harder battle) works three times without a crash or soft-lock.
- [ ] The art in the slice is final quality for what it shows; any placeholder is labeled as such in the build notes.
- [ ] Sound effects play on hits, the ultimate and victory.
- [ ] Three playtesters outside your team can explain what each hero does after one chapter.
- [ ] The build notes list every known bug and every deferred item from the matrix.

> Judge fun separately from completeness: A slice can pass every check and still be dull. Keep one criterion that is a judgment call, such as "I want to replay the boss with a different party", and discuss it openly instead of hiding it in a bug list. It is the most useful signal the slice gives you.

## Ways to buy a slice, and what they cost

| Route | What you get | When it fits |
| --- | --- | --- |
| Advanced Game + Launch, $2,999 | A polished first playable vertical slice in 10 business days, then the full bounded build (within 30 days) and a 30-day launch campaign | Your RPG is a bounded turn-based game and you want the slice as a checkpoint on the way to a released game |
| Core Game, $499 | A small, complete RPG-lite: one contained area, a short quest line, basic combat, small inventory | You want a released mini-game to test the theme and combat with real players before a larger build |
| Custom quote | A slice scoped as the first stage of a much larger RPG, with its own matrix and acceptance criteria | The full game needs online features, an open world or a large story, and the slice is a decision point before a large budget |

For context, one studio's 2026 estimate puts mid-core RPG development at $300,000 to $1,000,000 or more. Against that, a slice that shows whether battles are fun is cheap insurance. Our [RPG cost guide](https://dfygames.com/guides/rpg-cost) explains which features push a game from the package tiers into a custom quote, and the [RPG service page](https://dfygames.com/games/rpg) shows the example concept the matrix above is based on.

Sources: Innovecs Games, "How Much Does Mobile Game Development Cost in 2026?" https://innovecsgames.com/blog/mobile-game-development-cost/

## After the slice: deciding on the larger build

1. Play it yourself for a week, a few battles a day. Note when you stop wanting to play.
2. Collect playtester notes and look for the same complaint from several people.
3. Compare the slice against each acceptance criterion and mark pass or fail in writing.
4. Revisit the deferred column. Cut anything the slice showed is unnecessary, and move anything it showed is essential into the full-build scope.
5. Only then set the budget for the full game, using the slice as the quality bar in that contract.

Inside an Advanced build, feedback on the first playable feeds directly into the rest of the build, and refinements within the approved blueprint are unlimited until first submission. New systems are scope changes. If you are briefing the slice now, the [game brief template](https://dfygames.com/guides/mobile-game-brief-template) gives you a place to record the matrix.

## FAQ

**What is an RPG vertical slice?**
A thin piece of the game built to final quality: one complete battle loop, one progression step and a small amount of content. It shows how the finished game will feel before you fund the rest.

**How is a vertical slice different from a prototype?**
A prototype tests many systems roughly; a vertical slice finishes a few systems fully. For RPGs, the slice answers questions about combat feel and progression pacing that a rough prototype cannot.

**How much content should an RPG vertical slice include?**
Enough to repeat the core loop a few times: typically a handful of heroes, two or three enemy types, a boss and one short chapter. Everything else goes in a written deferred list.

**Does DFY Games deliver a vertical slice?**
Advanced Game + Launch includes a polished first playable vertical slice in 10 business days, followed by the full build within 30 days. A slice as the first stage of a much larger RPG is scoped by custom quote.

**Who owns the slice?**
After full payment you receive the game files and the original assets made for the project. Third-party software, fonts, SDKs and stock assets keep their own licenses.

## Related
- Service page: [RPG Game development](https://dfygames.com/games/rpg)
- [RPG game development: cost and scope](https://dfygames.com/guides/rpg-cost)
- [Mobile game design document template: what to put in your brief](https://dfygames.com/guides/mobile-game-brief-template)

## Sources
- Innovecs Games, "How Much Does Mobile Game Development Cost in 2026?" https://innovecsgames.com/blog/mobile-game-development-cost/

---
DFY Games (Done For You Games), https://dfygames.com. More guides: https://dfygames.com/guides · Index for AI assistants: https://dfygames.com/llms.txt