Why ATSYou refused to treat a technically valid CV as a finished product

The hardest decision I have made on this project was not a technical one. It was deciding that a system which did exactly what I had specified was not good enough to charge anyone for.

ATSYou tailors a CV you already have to a specific job advert. The central rule is that every sentence in the output must resolve to a claim you confirmed was true. If a line cannot be traced, the document is not delivered and you are not charged. That rule works. It has worked for months. ATSYou is still not open to customers.

What “working” actually got me

The provenance model is the part I am most confident about. Your CV is read once into a structured career profile in which every role, date, achievement and skill records the line of the original document it came from. You confirm each claim. Edit one and its confirmation is withdrawn until you confirm it again, which stops a quiet change from silently inheriting your earlier approval.

From there, tailoring is a selection problem rather than a writing problem. The advert asks for things; your profile either supports them or it does not. The free match report shows both halves — what matched, with the claim behind it, and what did not, left as a gap. Nothing gets added because an advert asked for it.

The document side was similarly clean. Four formats — PDF, Word, HTML and plain text — are each built from the same underlying model rather than converted from one another, so the plain-text version a parser reads is not a lossy print of the PDF. The model itself is single-column with no tables, no text boxes, no photograph and no date of birth. Those things do not need to be prohibited by a rule, because there is nowhere in the model to put them.

So: traceable, parser-safe, reproducible, tested. By every criterion I had written down in advance, it was finished.

The problem I had not written down

I read the output as a person applying for a job rather than as the person who built it, and the documents were lifeless.

Every sentence was defensible. Collectively they read like a database export with good grammar. A real CV has emphasis — it decides that this eighteen-month project matters more than that two-year job title, and it gives the important thing more room. My generator had no way to make that judgement, so it gave everything equal weight, which is the same as giving nothing any weight.

The specific failures, once I made myself list them:

• No sense of proportion. A six-week internship and a three-year role were rendered with the same density, because both were equally well-evidenced. Evidential strength and career significance are not the same axis, and I had only modelled the first.
• Layout that was safe rather than good. Single-column, parser-friendly and visually monotonous. Safe from a machine’s perspective; forgettable from a human’s. Both read it.
• Truthful phrasing that landed flat. Refusing to embellish is correct. But there is a wide gap between embellishing and writing well, and I had accidentally treated the two as the same thing — as though any sentence with energy in it must be an exaggeration.

Why I did not ship it anyway

The case for shipping was decent. The product was honest, the pricing was going to be pay-as-you-go with no subscription and no auto-renewal, people could see the price before confirming, and the free match report meant nobody would pay before seeing what they were getting. If a document was disappointing, the cost of that disappointment was a few pounds and a wasted evening.

The case against turned out to be stronger, and it came down to what the product claims about itself.

ATSYou’s whole argument is that it will not hand you something it cannot stand behind. That is the reason to choose it over a tool that will happily write you a better history. If I had shipped documents I would not have used myself, I would have been doing a quieter version of the exact thing the product exists to refuse — passing off output that met a specification as output that met a need.

There is a smaller reason too. A person tailoring a CV is usually doing it because they need work. That is not a good moment to be someone’s experiment in what counts as good enough.

What that costs

I should be straight about the price of this decision rather than presenting it as pure principle.

ATSYou has been publicly reachable for months without earning anything. Its pricing page currently says it is between published price books and has nothing to quote, and its footer says the legal terms are still being prepared and will appear before the product opens to customers. Both of those are true, and both are the visible surface of a decision that has kept a working system unmonetised.

I also cannot tell you when it opens. I have no date. Setting one would mean guessing at how long a quality problem takes to solve, and quality problems are precisely the kind that do not respect estimates.

What I would do differently

I would define done to include reading the output as its recipient, from the first week rather than the last. My acceptance criteria were all properties of the system — traceability, format fidelity, reproducibility — and every one of them was satisfiable without the result being any good. A specification made entirely of system properties will pass at exactly the moment the product stops improving.

The generator is not the hard part. It never was. The hard part is judgement about what matters in a particular person’s history, and I do not yet know whether that can be encoded, or whether ATSYou should be honest about needing a human somewhere in the loop. The status page will say which way it went.