What This Book Cannot Tell You

An early reader of this manuscript, a founder I have known for a decade and who read Part I on a long flight, wrote back with a single question. He did not ask about the method. He did not push on the name. He asked what the book was not going to tell him, and he asked it in a way that made clear he had been burned before by books that pretended to cover everything and covered nothing well. I sat with his email for an evening and wrote him a reply that was, embarrassingly, longer than the chapter he had just read. The reply is the spine of this chapter. I am going to make the same admission to you that I made to him, and I am going to make it early, because the reader who knows what a book is not for is the reader who gets the most out of what it is for.

Sculpting is a methodology for one specific gap: the one between a founder’s working prototype and a product that can be sold, supported and scaled. It is not a business philosophy, a career plan or a theory of the firm; it is a way of reading someone else’s half-finished garden and knowing what to prune, what to stake, what to leave alone and what to tear out entirely. If you hand a sculptor a block of marble and the sculptor produces a figure, you have not thereby been told anything about how to sell the figure, where to put it, how to hire the apprentice who will polish it or whether the figure should have been carved in the first place. You have been told how to get from block to figure. That is a real craft, and it is worth a book, but it is not the whole of art.

The things the book does not cover are the things the book cannot cover without becoming a different book. Marketing is the first of them. Distribution (which is not the same as marketing, and which I suspect will be the subject of the book that replaces this one) is the second. Hiring is the third. Fundraising is the fourth. And underneath all four, unaddressed here, is the largest and least comfortable question a founder ever asks themselves, which is whether the thing they are building ought to exist at all. Sculpting has nothing to say about that question. A sculptor who stops mid-block to ask whether the world needs another figure is a sculptor who does not finish the figure, and the book’s job is to help you finish.

I want to be specific about each of these exclusions, because vagueness at this point would be a cheat.

Marketing (the discipline of finding the people who would want a thing if they knew it existed and making sure they know it exists) is absent from this book because Sliday’s record in it is mixed at best. We have shipped products that deserved audiences and did not get them. We have shipped products whose audiences showed up without any particular effort on our part. I can describe the difference between those two outcomes but I cannot yet predict it, and writing a chapter on something I cannot predict would be dishonest.

Distribution is absent because it is the next book. Distribution Will Eat Sculpting argues that distribution is the bottleneck Sculpting exposes: that once any competent founder plus any competent studio can ship a polished product in eight weeks, the thing that becomes scarce is the audience that will care. This book names that bottleneck. It does not solve it. I know a handful of studios and founders running interesting experiments in agent-driven distribution, and I can point at a few patterns, but pointing is not a methodology. The honest line is: we see the shape of the problem, we do not yet see the shape of the answer, and we are not going to pretend to.

Hiring is absent because it is a trade I respect too much to fake. There are people who have spent their careers getting good at hiring, and their books are better than the chapter I could write. Building a team is related to Sculpting only in the way that commissioning a kitchen is related to cooking — the first enables the second, but the skills do not transfer. A studio that ships beautifully and hires badly goes out of business as reliably as one that hires beautifully and ships badly.

Fundraising is absent for a harder reason, which is that I have opinions about it that the argument of this book does not rest on. The relationship between a studio and a founder, the relationship between a founder and their prototype and the relationship between a prototype and a shipped product. These are what the book is about. The relationship between a founder and their cap table is a different book, and a more cynical one.

And the question of whether the product should exist is absent because that question belongs to the founder, and the studio that answers it on the founder’s behalf has overstepped. Sculpting assumes the founder has decided. If the founder has not decided, the studio’s job is to say so and send them away. We have done this. It is never a pleasant conversation. It is occasionally the best conversation we have had that year.

The second thing this book cannot tell you is which tools you should be using eighteen months from the day you read this sentence.

The tools cited in these chapters — Claude Code, Cursor, Twenty, n8n, AMUX, v0, Lovable, Bolt — are the tools I am using, the tools Sliday has adopted in production or the tools our clients are arriving with. Most of them did not exist in their current form three years ago. Most of them will have been renamed, acquired, forked or quietly deprecated three years from now. I have no particular attachment to any of them. I have named them because naming an abstract tool is useless, and because a reader in 2026 needs to see concrete examples to follow an argument and because pretending to be tool-agnostic in a book about tools would be a different kind of dishonesty.

The method will outlast the tools. The method is: the founder arrives with an over-engineered working prototype, the studio reads it, the studio subtracts, the studio hardens, the studio ships. That pattern does not depend on which editor the founder used, which model produced the first pass, which CRM the studio replaced, which agent framework orchestrated the deployment. The pattern depends on the economics of the prototype — that it is now cheap enough to be brought to the first meeting rather than produced over the first year — and the economics of the prototype are not going to reverse. Tools that make prototypes cheaper will proliferate. Tools that make prototypes slower will not survive. The method rides on the economics, not on any particular vendor’s quarter.

This is the reason the book is structured the way it is. Parts I through III are about the shift in economics and the role change it forces. Part IV is about the craft the new role requires. Parts V and VI are about who does the work and why it wants a name. Part VII looks past the immediate bottleneck to the next one. Only the examples require a specific vendor. The examples should be read the way you read a restaurant review from 2019: useful for the dish, dated on the chef.

If that means you are reading this book in 2028 and half the tool names have aged out, then the book has done its job. You are not meant to install my stack. You are meant to recognise your own.

The third thing this book cannot tell you (and here I have to be careful, because the instinct runs deep in the studio owner I have been for seventeen years) is how to become a Certified Sculpting Practitioner.

There is no such thing. There will be no such thing.

I want to dwell on this for a paragraph, because the reflex to turn a book into a programme, a programme into a certification and a certification into a foundation is the first reflex a studio owner who has written a book will feel, and it is the first reflex the book itself would cut. I have already been asked, in the three months this manuscript has been circulating, whether there will be a Sculpting Practitioner badge, a Sculpting Foundation website, a two-day training course with a PDF certificate, a tiered membership, an annual conference, a colour-coded levels system and (my personal favourite) a LinkedIn endorsement taxonomy. Each of these was proposed in good faith by someone who likes the book and wants it to do well. Each of them would be the beginning of the end of whatever the book is. The methodology described here is a description of work that is already being done, by people who did not read a book before they started doing it, and the last thing the world needs is a gatekeeping apparatus for the work those people are already doing without permission from me or anyone else.

The studios doing this well do not need a certificate. The founders being served by them do not ask for one. The employees adapting to the shift are not waiting for a curriculum. If Sculpting is a real thing — and I think it is — it will spread the way the scooter-bicycle-motorbike image spread, which is by being useful, by being quoted, by being borrowed without attribution, by being improved by people who have never heard my name. That is the success condition. A Sculpting Foundation would be the failure condition. If you ever see one, assume it was set up by someone who read this chapter and did the opposite.

The book is not a manifesto either. A manifesto asks the reader to sign up. This book asks the reader to notice something that is already happening and to find the language for it. There is no oath. There is no list of twelve principles pinned to a door. If you read the book and keep working the way you already work, nothing is lost. If you read the book and find one sentence that describes something you have been doing without a name for it, the book has paid its price.

What the book can do is point, usefully, at the books that cover the ground it does not.

For distribution, Ryan Holiday’s Perennial Seller is the one I would hand to a founder who has finished Sculpting and is asking what comes next.¹ It says nothing about software as such. It is about why some work finds an audience over years while technically better work does not, and it is written by someone who has watched the distribution game from inside the publishing industry long enough to be suspicious of shortcuts. Read it after shipping, not before.

For hiring, Michael Lopp’s Managing Humans is the one.² Lopp writes about the actual human beings who show up to work, not the abstraction management books usually address. The chapters on how to run a one-to-one and how to read a team in its second year are worth the cover price on their own. If you are a studio owner in year three and you have never thought systematically about how your team communicates, start there.

For craft — the philosophical ground underneath everything this book is about — David Pye’s The Nature and Art of Workmanship is the one.³ It is an older book, not about software, and it distinguishes between the workmanship of certainty and the workmanship of risk in a way that maps almost too cleanly onto the distinction between generated code and edited code. Pye is the quiet patron saint of this methodology without knowing it. If you read one book alongside this one, read Pye.

Three books. Not a syllabus. I could list twenty and be accurate and unhelpful; I have listed three and been accurate and, I hope, useful. If you want more, the bibliography at the back points further, but these three do the load-bearing work for the three gaps this book leaves open.

The honest thing to say, to close Part VI, is that most of what matters about running a software studio in 2026 is not a methodology problem at all. It is a taste problem, a judgement problem, a people problem, a timing problem, a distribution problem, a luck problem. Sculpting is a methodology for the part that is a methodology problem, and that part turns out to be smaller than the part it leaves behind. I would rather tell you that now, on page two hundred and something, than have you finish the book and feel misled.

Half of what is true about software in 2026 is not in this book, and that is the point.