How to Develop Your Own Cookie Recipe From Scratch
Most serious bakers reach the point where following other people's recipes is no longer enough. You have made enough cookies to understand what good ones feel and taste like, you have a sense of what makes a formula work, and you want to build something that is yours — a formula you can claim and reproduce and refine over time. This is the point where baking shifts from a skill into a craft, and the shift requires a different set of tools than recipe execution does.
Developing a cookie recipe from scratch is not the same as tweaking an existing one. Tweaking starts from a working formula and makes targeted adjustments within a known structure. Development starts from a concept and builds a structure to support it. The process is closer to experimental design than it is to cooking: you form hypotheses about what ingredients and ratios will produce a target outcome, test them in controlled conditions, observe the results accurately, and use what you learn to inform the next iteration.
This guide is written for bakers who are serious about this process. It covers every stage — from the initial flavor concept through ratio selection, test batching, variable isolation, systematic documentation, and final formula verification — with the specific frameworks and techniques that make the process reliable rather than hopeful.
Where Should a New Cookie Recipe Actually Start?
The most common mistake in recipe development is starting with ingredients rather than starting with a target. If the first decision you make is what butter to use or what flour to buy, you are working backward. The target should come first, and it should be specific enough to evaluate.
The right starting point is a flavor and texture concept — a description of what the finished cookie should be that is specific enough to test against. "A chocolate chip cookie" is not a concept. "A thick, soft-centered cookie with pronounced caramel notes from browned butter and brown sugar, a slight resistance at the bite that gives way to a gooey center, and a finish that lingers on the roasted-cocoa character of the chips" is a concept. The difference between these is the difference between a direction and a destination.
Building this concept requires two things before anything gets baked. The first is reference eating: deliberately tasting cookies that approximate the flavor profile or texture you are building toward, and tasting them analytically rather than just for enjoyment. What is the first thing you taste? What develops in the middle of the chew? What is the finish? Where are the contrasts — between sweetness and salt, between soft and crunchy, between rich and bright? Reference eating is not copying. It is calibrating your sensory target so you can evaluate your own formulas against something concrete.
The second is flavor mapping. Before mixing anything, write down the flavor notes your target cookie should have in order of prominence: primary (the dominant note that arrives first and stays loudest), secondary (the supporting notes that give the cookie complexity), and tertiary (the finishing notes that linger after the cookie is eaten). Named flavor compounds can help anchor this map: vanillin and 4-hydroxybenzaldehyde for vanilla character, cinnamaldehyde for cinnamon warmth, pyrazines (2,5-dimethylpyrazine, 2,3,5-trimethylpyrazine) for the nutty-roasted notes of browned butter, furaneol (DMHF) and diacetyl for the caramel and butter register, eugenol for the spicy depth in clove-adjacent flavors. These are not academic labels. They are specific enough to describe and specific enough to test: if your target includes a pronounced pyrazine note, you know you need browned butter or a Maillard-forward bake. If it includes furaneol, you know caramel development or a high-brown-sugar formula is part of the path.
The flavor map is not a recipe. It is the evaluation criteria you will use to assess every test batch. Write it before the first batch so your evaluation is against an objective target rather than against your impression of what you wanted.
What Are the Ratio Frameworks That Professional Bakers Use as Starting Points?
Cookie recipes are not collections of individual ingredient amounts — they are ratio systems where each ingredient's quantity is set relative to the others. Understanding this changes how you approach development, because it means the foundational decisions are about proportions, not measurements.
The professional tool for managing ratios is the Baker's Percentage. In this system, the weight of flour is set to 100 percent, and every other ingredient is expressed as a percentage of that flour weight. A formula might read: flour 100 percent, butter 75 percent, total sugar 90 percent, eggs 30 percent, leavening 0.75 percent, salt 1.5 percent. These percentages travel with the formula regardless of batch size and make it immediately clear what is changing between iterations. When you increase the butter from 75 to 85 percent, you know exactly what you have done and can predict its effect.
The starting ratios for different cookie style targets provide a framework for where to begin:
For a soft, thick drop cookie: flour at 100 percent, butter at 65 to 75 percent, total sugar at 85 to 100 percent (split approximately 60 to 40 between brown and white), eggs at 25 to 35 percent, baking powder at 0.75 to 1 percent, salt at 1.5 to 2 percent.
For a thin, crispy cookie: flour at 100 percent, butter at 80 to 100 percent, total sugar at 90 to 110 percent (weighted toward white), eggs at 20 to 25 percent, minimal or no leavening, salt at 1 to 1.5 percent.
For a cakey, tender cookie: flour at 100 percent, butter at 50 to 60 percent (softened and well creamed), total sugar at 80 to 90 percent, eggs at 35 to 50 percent (weighted toward whites), baking powder at 1 to 1.25 percent, salt at 1.5 percent.
For a fudgy, dense cookie: flour at 100 percent, butter at 80 to 100 percent (melted), total sugar at 90 to 110 percent (weighted toward brown), eggs at 35 to 50 percent (weighted toward yolks), minimal leavening or none, salt at 1.5 to 2 percent.
These are not recipes — they are starting frameworks. Every one of them needs refinement for the specific flavor profile you are building, and none of them will produce your ideal cookie in the first batch. But they give you a structurally sound starting point that is already producing recognizable cookies in the right general direction, which is a better position than beginning from scratch without a ratio foundation.
Knowing what each ingredient ratio controls is as important as knowing the ratios themselves. Butter-to-flour ratio is the single most impactful texture control lever: higher butter relative to flour means more spread, more tenderness, and a richer fat character. Sugar-to-flour ratio controls sweetness intensity and moisture retention. Sugar type (brown versus white) controls hygroscopicity: brown sugar's molasses content retains moisture through storage, while white sugar produces a crispier, drier result. Egg ratio controls structure and moisture: more whole egg produces more structure, more yolk produces tenderness and emulsification, more white produces rigidity and airiness. Leavening controls lift, spread, and browning: baking soda raises pH and accelerates the Maillard reaction (producing darker browning at lower temperatures), while baking powder provides more lift with a less significant browning effect.
How Do You Build and Bake Your First Test Batch?
The first test batch is an anchor, not an attempt at the perfect cookie. Its purpose is to give you a real, evaluated baseline against which all subsequent iterations can be compared. The anchor batch should be baked from the appropriate starting ratio framework for your texture target, with your primary flavor ingredients in place, but no unusual variables yet.
Scale everything by weight, not volume. A kitchen scale accurate to one gram is the minimum standard for recipe development. Volume measurements introduce variability of 30 percent or more for flour, depending on how the cup is filled, which makes controlled testing impossible. Weight measurements are exact and reproducible.
Record every detail of the anchor batch before baking:
Ingredient weights to the gram, including the weight of the empty mixing bowl before and after each addition if you want the most precise records.
Butter temperature at the start of mixing. This is not "softened" — it is a number. Sixty-six degrees Fahrenheit at the start of creaming is a different condition than 72 degrees, and it produces different air incorporation in the butter-sugar matrix.
Dough temperature at the end of mixing. Friction from mixing raises dough temperature, and a dough that finishes at 70 degrees versus 75 degrees will behave differently both at rest and in the oven.
Pan type, pan color, rack position, and whether parchment or a silicone mat was used. These variables affect heat transmission to the bottom of the cookie and change browning patterns.
Chill time, if any, between mixing and baking.
Portioning method (scoop size by number, or gram weight per portion).
Oven temperature as confirmed by an oven thermometer, not the dial. Most residential ovens run 25 to 50 degrees off from the dial setting.
Observe during baking at three-minute intervals: when does the cookie begin to spread, when do the edges begin to set, when does surface color appear, when does the top surface lose its wet sheen. Write these down with the clock time, not approximations.
After baking, let the cookies cool completely before tasting. Hot cookies do not taste like the same cookies at room temperature. At elevated temperatures, fat coats the palate and suppresses flavor perception. Aroma is more volatile and dominant when hot, creating a false impression of flavor intensity. Sweetness is more pronounced at warm temperatures, and bitter notes from cocoa or coffee are more subdued. The honest eating experience of your cookie is the room temperature one, and that is what you should be evaluating your formula against.
Taste the anchor batch systematically: appearance, aroma, the texture on the first bite, the flavor on the first bite, how the flavor develops through the chew, the finish, and the texture at the 24-hour mark. Write notes using specific language. "Sweet" is not useful. "Leading caramel sweetness that drops off quickly with little complexity in the middle" is useful.
What Should You Observe and Record During and After Each Test Bake?
Systematic observation is what separates recipe development from repeated guessing. The goal is to capture enough detail about each batch that you can trace the specific cause of each specific outcome when you look back at your records weeks later.
During baking, the most useful observation points are: when spread begins (early spread in the first three minutes indicates fat that melted too quickly, usually from dough that was too warm or from too-high butter ratio), when the edges set (late-setting edges indicate insufficient leavening or too much fat relative to structure-building ingredients), and when the surface transitions from glossy to matte (this is the moment when enough surface moisture has evaporated that the Maillard reaction can begin in earnest at temperatures above 212 degrees Fahrenheit).
After baking, the physical measurements that matter most are: diameter (spread), height at center (lift), and the ratio between the two. A cookie that spread two inches wider and dropped half an inch is telling you something specific about the balance between spread forces and structural setting. These are not qualitative impressions — measure with a ruler.
Taste evaluation should follow a consistent structure across all batches so that the notes are comparable. The framework that works best for cookie development has six components: appearance (color uniformity, surface texture, edge definition), aroma (what compounds you detect and in what sequence), texture at first bite (resistance, crunch or softness, whether the exterior and interior are differentiated or uniform), flavor at first bite (which notes arrive first and how intense they are), flavor development through the chew (what emerges or fades as the cookie is chewed and mixed with saliva), and finish (what lingers after swallowing and for how long). Write the evaluation at three time points: immediately after pulling from the oven (just for reference), fully cooled at room temperature, and 24 hours later.
The 24-hour evaluation is not optional. Many formula problems only become apparent after the cookie has rested: texture that firms too much (over-set gluten or excessive sugar crystallization), sweetness that becomes cloying (usually too little salt or acid to balance), and greasiness that accumulates on the exterior (fat migration from a too-high butter ratio or incorrect butter temperature during mixing) all show up most clearly at 24 hours rather than immediately after baking.
Why Should You Only Change One Variable at a Time?
The isolation principle is the foundational rule of controlled experimentation, and it is the rule that most home bakers break most often in recipe development because it feels inefficient. You identified three things you want to change — why not change all three at once and get there faster?
Because if you change three things and the next batch is better, you do not know which of the three changes produced the improvement, or whether all three were necessary, or whether one of them actually made things worse and the other two overcame its negative effect. And if the next batch is worse, you have even less information. Every batch is a data point, and a data point you cannot interpret is wasted.
Changing one variable at a time means that each batch answers a specific question: does more brown sugar produce the moisture retention I want? Does increasing the butter-to-flour ratio from 70 percent to 80 percent produce too much spread for this formula? Does browned butter add enough pyrazine character to hit the roasted note in my target, and does the accompanying 15 to 20 percent moisture loss require adjustment of the other liquid ratios? Each of these is a separate test, and each produces information you can use with confidence.
The counterpart to variable isolation is the control batch. When testing a variable, bake a portion of the unchanged formula alongside the test batch. Tasting them side by side eliminates the memory distortion that comes from comparing a batch today to your recollection of the anchor batch from two weeks ago. Direct comparison in the same tasting session is far more reliable than sequential comparison across sessions.
The variable isolation rule has one practical exception: process variables that must travel together. If you are changing from softened butter to browned butter, you are simultaneously changing the fat's temperature profile, its moisture content (browned butter has lost 15 to 20 percent of its water weight), and its flavor compound concentration. These changes cannot be practically separated. Treat them as a single compound variable and document all of them together.
Which Variables Have the Biggest Impact and Which Should You Test First?
Not all variables produce equal effects, and understanding the impact hierarchy helps you prioritize the test sequence. Start with high-impact variables so the formula reaches its general target efficiently, then refine with lower-impact variables toward the end of the development process.
High-impact variables, in approximate order of their effect on the overall cookie outcome:
Fat type and state. The difference between softened creamed butter, melted butter, and browned butter is not a subtle flavor adjustment. It is a fundamental change to the dough's air content, moisture level, and fat compound composition. This variable has the most impact per change of any in a cookie formula and should be established early.
Sugar ratio and type. The split between brown sugar and white sugar affects moisture retention, surface browning, flavor register, and spread behavior in ways that compound across the entire formula. Getting this ratio right is a foundational step before refining other variables.
Fat-to-flour ratio. The single most reliable lever for controlling spread and richness. Each five-percentage-point change in butter relative to flour produces a meaningfully different cookie.
Egg ratio. The balance between whole eggs, extra yolks, and extra whites controls the tradeoff between structure (egg whites) and tenderness and emulsification (egg yolks). A formula at 30 percent eggs with two whole eggs is different from a formula at 30 percent eggs with one whole egg and two yolks in ways that cannot be recovered by adjusting other variables.
Flour quantity. Reducing flour by 10 percent relative to the anchor batch moves the cookie toward the fudgy end of the texture spectrum. Increasing it by 10 percent moves it toward the cakey end. This is a clean, isolatable test with predictable directional results.
Medium-impact variables:
Leavening type and quantity. Baking soda versus baking powder versus a combination, and the quantity of each, affects lift, spread, and browning. Baking soda's alkaline pH accelerates Maillard browning by catalyzing the reaction between amino acids and reducing sugars. This is worth testing once the fat and sugar ratios are established, but it is not the first variable to dial in.
Chill time and dough temperature. The length of time the dough rests in the refrigerator affects spread (via fat solidification) and flavor (via sucrose inversion and Maillard precursor development). Testing this variable means baking portions of the same dough at different chill times and comparing the results.
Lower-impact variables to test last:
Salt quantity. Salt suppresses bitterness perception by interfering with bitter taste receptor signaling — specifically through sodium ion interference with bitter receptor transduction — and amplifies sweetness and complexity. It is a significant flavor variable, but its effect is directionally predictable: too little and the cookie tastes flat; too much and it becomes savory. Adjust this in the final stages rather than early.
Vanilla quantity. Vanillin and related compounds in vanilla extract or paste contribute depth and aromatic complexity that reads as richness even in non-vanilla-forward profiles. Small increases (from one teaspoon to two teaspoons in a standard batch) produce noticeable changes in the finish but do not affect texture or structure.
Mix-in distribution. Adjusting how chocolate chips, nuts, or other mix-ins are incorporated and distributed is a low-impact late-stage variable once the base formula is established.
How Do You Document Results in a Way That Actually Helps You?
Documentation is the part of recipe development that most people handle inadequately, and inadequate documentation is why many bakers feel like they are always starting over. Good documentation means that every batch you have ever baked is available to inform every batch you will bake in the future.
The minimum documentation for each test batch is: a unique batch identifier (date plus iteration number is sufficient), the complete formula in Baker's Percentage, every process variable noted above, and structured tasting notes at room temperature and 24 hours.
Beyond the minimum, the most useful addition is a specific assessment of which aspects of the batch moved toward the target and which moved away from it, followed by a single clear hypothesis about what change to make next and why. "The spread was too aggressive, likely from butter that was too warm at mixing (measured 73 degrees at start). Next test: same formula, butter at 66 degrees, otherwise identical." This turns each batch into a stepping stone rather than a data point that has to be re-interpreted every time you look back at it.
Photographs are undervalued in recipe development records. A photograph of each batch at the same stage — on the cooling rack, immediately after baking — provides a visual record of spread, color, and surface texture that your written notes will not fully capture. The ability to look at photographs of batches 2, 5, and 9 side by side is often the clearest way to see the direction of change across an iteration sequence.
The failed batch archive is the record that most bakers do not keep and should. A formula that was abandoned because it spread too flat, crumbled, or had an unbalanced flavor is still valuable information. If the formula and notes are not recorded, you have no way of knowing whether you accidentally approach the same wrong formula in a future development process — and you have no ability to revisit a failed batch from a different starting context and recognize that it was actually closer to a different target than the one you were working toward.
How Do You Know When a Formula Is Done?
One of the signs of developing judgment as a recipe developer is knowing when to stop iterating. Two failure modes bracket this decision: stopping too early (before the formula has reached its target) and continuing too long (making increasingly small adjustments to a formula that has already arrived).
The convergence signal for a formula approaching its target is that each iteration produces smaller improvements and the remaining issues feel like matters of preference rather than structural problems. When you find yourself debating whether the brown-to-white sugar ratio should be 60-40 or 65-35, you are likely in preference territory rather than structural problem territory, which means the formula is close to done.
The check against stopping too early is to evaluate the formula explicitly against the flavor and texture concept you wrote before the first batch. Pull it out, read it, and score the current formula against each element of the concept. If most elements are met and the remaining gaps are small, you are in the final refinement stage. If multiple core elements of the concept are still unmet, you have more meaningful iterations to complete.
When you believe the formula has reached its target, bake it twice without consulting your notes — first to confirm you can reproduce it from memory, then with the written formula to confirm the written formula produces the result you experienced in the previous batch. A formula that only produces good results when you make it is not a finished formula. A formula that produces good results when someone else makes it from your written recipe is finished.
The replication test also reveals specification gaps in the written recipe. If the replication batch comes out differently from the development batch, something is underspecified: an ingredient weight, a process temperature, a timing detail, or a technique description that assumed knowledge the written recipe does not provide. These gaps need to be filled before the recipe is considered complete.
How Does Recipe Development Work When You Are Building a Stuffed Cookie?
Stuffed cookie development adds a second variable system — the filling — that has to be developed in parallel with the dough rather than as an afterthought. A stuffed cookie is a two-material design problem, and both materials need to perform well independently and together.
The dough development process is the same as for any cookie, with one additional constraint: the dough must be structurally capable of encasing a filling, holding it through assembly and baking, and maintaining the seam without breakthrough or deformation. This structural requirement pushes stuffed cookie dough toward specific characteristics — enough gluten development to resist deformation during assembly, enough thickness to act as a thermal barrier for the filling, and enough cohesion to seal without cracking. The ratio choices that optimize for stuffed cookie structure are not always the same as those that optimize for the ideal flavor and texture of the dough eaten alone.
The filling development process is a parallel track with its own iteration sequence. The filling has its own target: what does it taste like, what is its texture at the temperature it will be eaten, how does it behave when heated inside the baking dough, and does it remain at its intended consistency at room temperature versus refrigerator temperature versus eating temperature?
Filling stability during baking is the most technically demanding element. A caramel filling must maintain its emulsion through the bake cycle without breaking and separating into a greasy, grainy result. A ganache filling must stay cohesive through the temperature range the cookie experiences without the fat separating. A cream-based filling must not coagulate at baking temperatures. Each of these is a formulation problem with specific ingredient-level solutions (emulsifiers, stabilizers, correct chocolate-to-cream ratios for ganache) that require their own iteration sequence.
The combined test is the step that most reveals unexpected interactions. A dough that is excellent by itself and a filling that is excellent by itself may produce a combined cookie that does not taste right because the flavor balance between them is off. If the dough is too sweet, the filling's complexity is buried. If the filling is too dominant, the dough becomes a neutral vehicle rather than an active contributor to the eating experience. The target flavor balance varies by flavor concept, but in most stuffed cookie formulas, the dough should contribute flavor complexity in the background while the filling delivers the cookie's primary flavor statement. Testing the combination and adjusting both toward that balance is the final stage of stuffed cookie development.
The seam test is worth doing explicitly: assemble a batch using the final assembly method, chill, and bake. Evaluate whether the seam held, where the dough wall was thinnest and whether it survived, and whether any filling leaked through the bottom. These structural tests are separate from flavor evaluation and should be documented with the same rigor.
How Fat and Weird Cookie Approaches Recipe Development
Every flavor in the Fat and Weird Cookie lineup began as a concept before it became a formula. The concept describes the eating experience in enough detail to evaluate each test batch against it, and the development process moves through structured iterations with documented hypotheses rather than adjustments made by feel.
The parallel development of dough and filling formulas is part of what makes the stuffed cookie format as demanding to develop as it is rewarding to eat. Getting the dough right and the filling right is not enough. Getting them right together, balanced in flavor and texture so that the combination produces the intended experience from first bite to finish, is the actual goal — and that requires the same rigorous, systematic approach applied to two formulas simultaneously and ultimately to their combination.
The archive of failed and partially-developed formulas at Fat and Weird Cookie is as valuable as the active lineup. It contains formulas that were abandoned because they did not hit the intended target, but also formulas that were abandoned because the timing was not right or because a different direction looked more promising at the time. Some of those formulas are still candidates for future development, and the complete records of each make it possible to return to them with current knowledge rather than starting over.
If you are beginning your own recipe development process, the most important thing to internalize is that the goal of each batch is information, not the perfect cookie. The perfect cookie comes from accumulating enough information to know precisely what to make. Treating every batch as a data point rather than a result changes how you bake and how quickly you get to formulas worth keeping.
Frequently Asked Questions
Where do you start when developing a cookie recipe from scratch?
Start with a written target, not with ingredients. Before anything goes into a bowl, describe what the finished cookie should taste and feel like in specific terms: the flavor notes in order of prominence, the texture you are aiming for (thick and soft, thin and crispy, fudgy and dense), and any contrast elements that are part of the concept (a crunchy exterior with a soft center, a roasted bitterness balanced by caramel sweetness). This concept becomes the evaluation criteria for every test batch. Without it, you are adjusting without a clear target and cannot reliably assess whether any iteration is moving toward or away from what you are trying to build.
What is Baker's Percentage and why should home bakers use it?
Baker's Percentage is a ratio system in which flour weight is set to 100 percent and every other ingredient is expressed as a percentage of that flour weight. A butter quantity of 75 percent means 75 grams of butter for every 100 grams of flour. The value of this system in recipe development is that it makes ratios portable across batch sizes and makes the effect of each variable change immediately legible. When you increase butter from 75 to 85 percent, you know exactly what changed and can predict its directional effect. Without a ratio system, it is easy to lose track of what changed between batches and why a specific iteration produced a different result.
How many test batches does it take to develop a good cookie recipe?
There is no fixed number, but most original cookie formulas from a craft-level starting point require between five and twelve test batches before they reach a final state worth documenting. Simpler texture targets with well-understood ingredient combinations reach the final formula faster. Complex flavor combinations, unusual ingredient ratios, or formats with specific structural requirements like stuffed cookies require more iterations. The number of batches is less important than the quality of information extracted from each one. A well-documented batch that answers a specific question clearly is worth more than two batches that were baked without clear hypotheses and evaluated without structured notes.
Why is variable isolation so important in recipe development?
Because it is the only way to know what caused a specific outcome. If you change three variables between batches and the batch is better, you have not learned which of the three changes caused the improvement, or whether all three were necessary. If the batch is worse, you cannot identify which change to reverse. Every batch should answer one specific question, which means every batch should change exactly one variable from the previous batch. The control batch baked alongside each test batch makes the comparison direct and eliminates the distortion of comparing a current batch to a remembered previous one.
How do you know when a cookie recipe is finished?
A recipe is finished when it meets the target criteria established at the beginning of the development process, can be reproduced by following the written recipe without insider knowledge, and produces the same result across two consecutive replications. The convergence signal that you are close to done is that each iteration produces smaller improvements and the remaining gaps feel like preference questions rather than structural problems. Before declaring a formula finished, bake it once without consulting notes, evaluate it against the original concept, then bake it again from the written recipe. Both batches should produce the same result. If they do not, the recipe has specification gaps that need to be filled.
Should you taste cookies hot or at room temperature when evaluating them?
Always at room temperature, with a second evaluation at 24 hours. Hot cookies taste significantly different from room temperature cookies because of how temperature affects flavor and texture perception. At elevated temperatures, volatile aromatic compounds are more intense, sweetness is amplified, fat coats the palate and suppresses some flavor development, and the texture of the starch matrix is in its softest, most gelatinized state. The room temperature cookie is the honest version of the formula, and evaluating it hot instead of fully cooled leads to development decisions that are based on a temporary state rather than the eating experience the cookie actually produces.
What should you do when a test batch completely fails?
Document it with the same rigor as a successful batch, and write a specific hypothesis about what caused the failure. A completely failed batch — one that spread flat, crumbled, tasted wrong, or had the wrong texture — contains as much information as a near-successful one, and sometimes more. The failure modes that are most visible (flat spreading, crumbling, gumminess) are the ones with the clearest causes and the most direct fixes. Add the failed batch to your archive with complete notes rather than discarding the records. Failed formulas are the record of the solution space you have already explored, and without them, future development can accidentally revisit the same failing formulas.
How does developing a stuffed cookie recipe differ from developing a standard cookie recipe?
A stuffed cookie is a two-formula development project. The dough and the filling are each developed through their own iteration sequences, with their own concept descriptions and their own test batches, and then combined in a third stage where the interaction between them is evaluated and adjusted. This is more complex than standard cookie development because a dough that works well alone may not produce the right flavor balance against a specific filling, and vice versa. The stuffed cookie format also adds structural requirements to the dough that are separate from flavor and texture considerations: the dough needs to hold a filling through assembly, survive baking without the filling breaking through, and maintain its seam integrity through cooling and handling. These structural requirements become part of the dough's evaluation criteria alongside flavor and texture.
Fat and Weird Cookie is an independent stuffed cookie bakery where every formula in the lineup was developed through the process described in this guide: a written concept, structured test batches with one variable changed at a time, documented results at each iteration, and parallel development of the dough and filling as a combined system. The records from that process, including the failed batches and abandoned directions, are part of what makes the active formulas reproducible across every production run.
