A Better MTG Deckbuilding Workflow: Search, Build, Analyze, Goldfish, Repeat

TLDR: A useful MTG deckbuilding workflow is a loop: define the deck’s job, build a baseline, verify legality, audit its mana and functional roles, inspect possible combos, test opening hands, goldfish early turns, play relevant games, and make one coherent revision. Preserve each baseline so you can tell whether an edit helped instead of endlessly rearranging the same 12 cards.

The purpose of an MTG deckbuilding workflow is not to let a tool declare that your deck is good. It is to make your decisions visible and repeatable. A deck builder can organize the list, an analyzer can expose structural pressure, and practice games can reveal what actually happens. You still decide whether a card supports the plan, whether a hand is keepable, and whether a combo belongs at your table.

The complete deckbuilding loop

Stage	Question to answer	Useful output
1. Brief	What is this deck trying to do?	Format, environment, plan and constraints
2. Discover	Which cards could perform each job?	Baseline list, test candidates and maybeboard
3. Verify	Is the list legal and rules-correct?	Checked format, card text and restrictions
4. Analyze	Can the deck deploy its plan reliably?	Curve, land, color and role questions
5. Inspect	Are there synergies or combo lines to evaluate?	Documented interactions and package decisions
6. Practice	What do opening hands and early turns look like?	Mulligan and sequencing observations
7. Play	What fails under relevant opposition?	Game notes tied to a list version
8. Revise	What is the smallest coherent change to test?	New version and a specific hypothesis

These stages are connected. A color problem found during goldfishing sends you back to the mana audit. A dead card in several matchups sends you back to discovery. A combo scan may reveal that two individually reasonable cards create an interaction your Commander pod does not want. The loop is the feature; reaching a supposedly finished list is not.

1. Write a deck brief before searching for cards

Start with a short brief that prevents the deck from becoming a pile of unrelated good cards. Record the format, intended environment, primary plan, backup plan, budget or collection constraints, and any cards that must be included. For Commander, include the kind of game the pod expects. For Constructed, name the matchups or tournament field the list must face.

Format and applicable card pool
Expected pod, local metagame or testing field
Primary way the deck creates an advantage or wins
Secondary plan when the first plan is disrupted
Budget, collection or event constraints
Non-negotiable cards and cards included only as experiments

Make the plan specific enough to guide cuts. “Blue-red spells” describes colors and card types. “Apply early pressure, protect a compact threat, and finish with efficient reach” describes jobs. When two cards compete for a slot, the second statement gives you a basis for choosing.

2. Discover cards and build version 0

Use card and set search to build a broad candidate pool, then assemble the first playable baseline in a deck builder. MTGApp’s documented tool set supports card search, list organization, curve and color views, land-count inspection, opening-hand tests, mulligans, goldfishing, sharing and export. Version 0 does not need to be elegant. It needs to be coherent enough to test.

Organize cards by function as well as conventional card type. A Commander list containing ten artifacts tells you less than a list showing which artifacts accelerate mana, draw cards, protect the commander or enable a win. Functional categories expose overloaded sections and missing jobs.

Plan enablers: cards that make the central strategy function
Payoffs or finishers: cards that convert the plan into a decisive advantage
Mana: lands, fixing and acceleration
Card access: draw, selection, tutors or recursion
Interaction: removal, counters, disruption and sweepers
Protection and resilience: ways to preserve or rebuild the plan
Flex slots: metagame choices and cards under evaluation

Keep a separate maybeboard. A card placed there is not rejected forever; it simply lost the current slot competition. Add a short note such as “cheaper graveyard interaction” or “test if four-mana draw is too slow.” This is far more useful than rediscovering the same card during every late-night editing session.

3. Verify rules, legality and format constraints

Before tuning performance, confirm that the deck is valid for its intended format. Use Wizards’ live official Magic rules resources for rules questions and current card information, then check the Banned & Restricted list for sanctioned Constructed play. Wizards states that these restrictions are format-specific and that banned cards cannot appear in a deck or sideboard for sanctioned play.

Commander adds construction constraints including a 100-card deck, singleton construction apart from basic lands, and commander color identity. Those rules establish whether the list is valid; they do not determine whether its speed, combos or interaction suit a particular group. That remains a player and pod decision.

4. Analyze the curve, mana and functional balance

A mana-curve chart is a diagnostic, not a grade. It shows where mana values cluster and can prompt questions about early plays, expensive cards and sequencing. It cannot determine whether a six-mana spell is essential, whether cost reduction will apply, or whether the deck’s interaction lines up with its opponents. The deck builder manages the list, while the analyzer helps interrogate its structure.

Review the curve beside land count, acceleration and colored requirements. There is no universal mana formula; strategy and expected opposition affect mana decisions. If the deck feels clunky, use a structured mana-curve diagnosis rather than automatically cutting the most expensive card.

Can the deck make a relevant play during its intended early turns?
Do its expensive spells have enough ramp, setup or game impact to justify them?
Can the available lands and fixing produce the required colors on time?
Are conditional lands, modal cards or mana creatures being counted realistically?
Does card draw help recover from flooding, or does it merely add more expensive spells?
Are key functional roles concentrated at the same mana value?

Separate four problems that often look identical

A spell stranded in hand does not automatically prove that the deck needs more lands. The deck may lack total mana, the correct color, useful early sequencing or enough inexpensive action. Record which failure occurred.

Observed problem	Likely question
Missed land drops	Is the land count, draw package or mulligan standard appropriate?
Enough lands, wrong colors	Does the source mix support early colored requirements?
Mana available, nothing useful to cast	Is the curve or functional distribution too top-heavy?
Castable hand, weak development	Are card choices or sequencing failing to advance the plan?

This distinction stops a common editing spiral: adding lands to solve a color problem, cutting lands after flooding once, and then blaming the curve when the revised deck misses its third land drop.

5. Scan for combos without confusing them with synergy

Search the list’s important cards in the combo database to identify documented interactions. MTGApp presents the database as a resource for researching combo lines. Finding a line is only the beginning of the decision.

Label what you found. Synergy makes cards better together. An engine repeatedly generates resources. A loop repeats an interaction, sometimes without winning. A lock restricts meaningful opposing actions. A deterministic win package produces a defined game-ending result under stated conditions. Calling all five “combos” makes the deck harder to evaluate and the pregame conversation less informative.

For each deliberate package, record its number of slots, mana requirements, setup, points of disruption and usefulness when drawn separately. In Commander, also ask whether its speed and resilience match the expected pod. Legal does not automatically mean suitable, and technically infinite does not mean conveniently executable.

6. Test opening hands and goldfish early turns

Draw repeated opening hands using the mulligan procedure applicable to your format and event. Do not score a hand merely by counting lands and spells. Ask whether it has the colors, timing and functional pieces needed to participate in the game. The opening-hand decision workflow can help separate attractive cards from an actually workable hand.

What is the hand’s first meaningful play?
Can it produce the required colors when they are needed?
What does it do if its first threat or engine is answered?
Which draw would improve it, and how many realistic draws qualify?
Would you keep it against an unknown opponent?
Would the answer change on the play, on the draw or in a known matchup?

After the keep decision, goldfish several early turns. Speak or write the sequence: land, spell, target and remaining mana. This catches awkward tapped-land sequences, competing color requirements and turns where the curve looked fine on a chart but cannot be deployed cleanly.

Goldfishing is best for checking mana access, sequencing and the speed of an unopposed plan. It does not reproduce removal, counterplay, combat decisions, multiplayer politics or sideboarding. If the deck only functions when no opponent interacts, you have identified a useful warning—not proven a winning strategy.

7. Play relevant games and keep a lightweight log

Real games test assumptions that charts and solo draws cannot. Keep the log short enough that you will actually use it. Record the list version, matchup or pod, play/draw position where relevant, mulligan, mana issues, cards stranded in hand, decisive turn and one proposed explanation.

Do not use raw wins and losses as the only measure. A correct keep can lose to variance. A flawed list can win because an opponent stumbled. In multiplayer, threat assessment and table politics add even more noise. Look for repeated mechanisms: the same missing color, an interaction package that arrives too late, or a threat that never advances the stated plan.

There is no universal number of games that validates a deck change. The appropriate sample depends on the problem and testing conditions. A clear rules or legality error can be fixed immediately; a suspected matchup weakness needs repeated testing against that matchup. Use a problem-based testing threshold rather than waiting for an arbitrary game count.

8. Make the smallest coherent revision

Turn each edit into a hypothesis: “Replace two expensive reactive spells with cheaper interaction because the deck is consistently unable to affect turn two.” Save the current list as a baseline, create the next version, and retest the situation that prompted the change.

Changing one card at a time is useful when testing direct substitutes, but connected packages should move together. Removing a payoff may reduce the value of its enablers. Adding a new color requirement may require several mana-base edits. The goal is not literally one card per revision; it is one understandable idea per revision.

Name the observed problem.
Write the most likely explanation.
Choose the smallest card or package change that tests it.
Save the old list and label the new version.
Repeat the relevant hand, goldfish or matchup test.
Keep, revert or refine the change based on the new evidence.

How the workflow changes by format

Commander

Add commander access, color identity and multiplayer expectations to the brief. Evaluate whether the deck can function when its commander costs more after removal. Combo and lock packages deserve an explicit pod-fit check, while game logs should note whether a problem came from deck structure or table dynamics.

Constructed

Give matchup coverage and sideboarding more weight. Build a representative testing field rather than repeatedly facing whichever deck is nearby. A structured Constructed testing gauntlet helps distinguish a general flaw from a bad but acceptable matchup. Log preboard and postboard games separately because they test different configurations.

Limited

Put draft or sealed-pool construction before the shared audit loop. Draft practice should improve pick flexibility, signal reading, curve construction and recognition of when an early plan is no longer open. After drafting, organize the pool by role, build the mana base, inspect the curve, test hands and record which cards underperformed. The lessons then feed into the next draft rather than a permanent deck version.

Copyable MTG deckbuilding workflow checklist

Write the format, environment, plan and constraints.
Search for candidates and sort them by functional role.
Build and save version 0; place uncertain cards in a labeled maybeboard.
Verify current rules, card text, legality and format restrictions.
Inspect the curve, land count, colored sources and role distribution.
Research known interactions and decide whether each package fits the deck and environment.
Test opening hands and record why you would keep or mulligan.
Goldfish early turns to examine sequencing and mana access.
Play relevant games and log repeated mechanisms, not just results.
State one hypothesis and make the smallest coherent revision.
Save the new version and retest the condition that prompted the edit.
Repeat from discovery when the evidence points to a missing role or better candidate.

Build evidence, not just a bigger maybeboard

The best deckbuilding process does not eliminate judgment. It gives judgment better inputs. Start with a clear brief, use tools to organize and inspect the list, practice the decisions that happen before interaction, and then test against real opposition. Keep each revision tied to an observed problem and a stated hypothesis.

Your next step is simple: save the deck as version 0, draw an opening hand, and explain exactly what the first three turns are supposed to accomplish. If that answer is unclear, you have already found the first useful question for the loop.