Three copy directions for the homepage
and the solutions surface

Positioning statement

Cloudmaven is a CFO advisory firm that combines ERP, EPM, CRM, HCM, finance operations and AI-supported automation into scalable, integrable solutions.

Assembled from the homepage's own card row and closing offer trio — src/data/baseline/pages/index.json

Example hero block

src/data/baseline/pages/index.json — h1 and hero paragraphs

The pain-point entry it leads with

None. This is the honest answer and it is the direction's defining property. The page opens on capability and credential. The nearest thing to a named difficulty — “less manual effort”, “Less administration”, “processes that work automatically for you” — sits well below the fold and is phrased as an outcome of buying, not as a situation the reader recognises. A visitor who arrived because their close is painful has to read past the offer to find out that Cloudmaven knows about it.

src/data/baseline/pages/index.json — “We integrate your systems”, efficiency band, “Start every day…”

What stays from current copy

All of it, in its current order. The only edits are defects that this repository has already recorded against the live site:

• The shared page title. The live site puts one title on many pages, the homepage among them; the port already replaces it with the page's own H1. src/data/baseline/title-changes.json
• The heading-level skip. The homepage goes from its H1 straight to the H3 card row, which reparents everything under it for a screen reader and for every content extractor. The port records this pattern across the site. docs/baseline-port-2026-08-11.md
• Brand casing. “Cloudmaven”, one capital, everywhere — a build gate fails on the alternative. docs/lab-aispecify (src/pages/lab/aispecify/_README.md)
• The two figure bands are a decision, not a defect. The homepage carries a “Cloudmaven in Figures” band and an efficiency band. Whether each figure is sourced is a separate question this lane cannot answer, and the standing rule against unsourced figures is explicit in the e-flow source: “No outcome figure appears above — the published case studies carry none, and we do not invent them.” Under this page's own no-numbers rule the bands are not reproduced here. KEEP means keep them; it does not mean this lane has verified them. docs/design/2026-08-12-claude-design/e-flow.html

What to judge — the one/three/thirty-second rule

• At one secondThe reader can name the category: enterprise finance software and consulting. They cannot yet tell whether it is for them.
• At three secondsWeakest point. There is no verb and no consequence — nothing has broken, nothing has been repaired. The sentence describes a seller.
• At thirty secondsStrongest point. The scope is complete and legible: solutions, integrations, service, proof, people, a next step.

The rule is Christoph's, relayed as binding in review/codex-homepage-x1-x3/DIRECTION.md where it governs illustration. Applying it to copy is this lane's own extension of it, and should be read as a proposal too.

Positioning statement

The systems are not the problem — the space between them is, and Cloudmaven works on the handoffs where finance stalls.

docs/design/2026-08-12-claude-design/e-flow.html — “the systems are fine, and the space between them is where the month goes”

Example hero block

e-flow.html — “Your close is not slow because your people are”; “a person re-keying, exporting, or emailing a file so that two systems can agree”; the reconciliation file labelled “The actual system of record” docs/lab-aispecify variant A — “Invoices arrive by email. Payment approvals happen in Monday.com. Bank reconciliation happens in Excel.”

Variant A names the two third-party tools. The draft above generalises them, because a named board vendor on Cloudmaven's own homepage is a positioning decision the lane has no source for. Restoring the names is a legitimate alternative and would be faithful to the source.

The pain-point entry it leads with

The spreadsheet in the middle of the company. One reconciliation file that every system defers to, kept alive by hand, held by somebody who cannot take holiday in the first week of the month. It is the entry because it is the most physical of the sourced pain points and the one a finance operator recognises without being told what it means.

Behind it, in order, the material supplies the rest of the ladder: manual gates — the points where somebody has to touch it before the data can move; re-keying and CSV handoffs — CRM data crossing into the ERP as a file; a recurring report rebuilt by hand — the board pack assembled from exports, where two people produce two versions of the same number and both are defensible; and approval chains living outside the ledger — the invoice approved on a board, then entered into the core system a second time.

e-flow.html — “Manual gate — someone has to touch it”; “a spreadsheet in the middle of the company”; “The board pack is rebuilt from exports”; “Two people produce two versions of the same number, both defensible”; “somebody who could not go on holiday in the first week of the month” docs/lab-aispecify variants A and C — the shared invoice inbox, the approval board, the Excel reconciliation, the CRM CSV export, the recurring report rebuilt in Excel

What stays from current copy

• “Start every day with business processes that work automatically for you.” It survives intact and moves up — it is the current page's only line that already speaks about the reader's day.
• “Which systems would you like to connect with each other?” Kept as written. It is a question addressed to the reader, which is exactly this direction's grammar.
• The named pre-built integrations and the middleware sentence. Specific, checkable, and the concrete answer to the jam the hero just described.
• The customer testimonials, verbatim. They are the only quoted material on the page and they already speak in pain-and-relief terms.
• The closing offer trio and the contact block. Unchanged; after a pain-led opening the reader needs the full scope somewhere, and this is where the current page already puts it.

src/data/baseline/pages/index.json

What to judge — the one/three/thirty-second rule

• At one secondStrongest point. The reader recognises a situation before they know who is speaking. Risk: they may not yet know this is enterprise software at all.
• At three secondsVerb and consequence are present and explicit — it jams, a person re-keys, the file becomes the record. This is what the rule asks for.
• At thirty secondsWeakest point. Scope has to be rebuilt after the pain — does the reader still learn that ERP, EPM, CRM, HCM, integrations and ongoing service are all here?
• Also judgeWhether a CFO reads a named jam as insight or as an accusation about their own house. The material assumes insight; nothing in the sources tests it.

Positioning statement

Cloudmaven answers on the whole surface a CFO's numbers cross — ERP, EPM, CRM and HCM — rather than on the one system in front of the question.

src/data/baseline/pages/index.json — “Our focus is not on individual tools, but on the overall picture of the financial architecture”; “Cloudmaven combines ERP, EPM, CRM, HCM, finance operations and AI-supported automation”

Example hero block

e-flow.html — the EPM / ERP / CRM / HCM layers; “Process, tool, automation, AI. We do not skip one”; “The damage happens when a stage gets skipped” src/data/baseline/pages/index.json — “the overall picture of the financial architecture”

The pain-point entry it leads with

Answers the system cannot give. Not a broken process but an unanswerable question: the board pack rebuilt from exports every quarter, two defensible versions of the same number, planning happening outside the system in a workbook. The reader's problem here is that nobody they have asked can see far enough across the landscape to settle it — which is precisely the gap this direction claims to fill.

The supporting move is the questions the material says are worth asking any partner in the room: who writes the process map, and when — because if the answer is “during the project”, the price in front of the buyer is an estimate of work nobody has scoped yet; and when did you last recommend a rival system — because every partner calls its recommendation independent and far fewer can date the last time being right about it cost them the licence revenue.

The source lists a third question, about which named person is still on the engagement late in the project. It is deliberately not used: it is a consultant-permanence question, and permanence promises are out of bounds for this direction.

e-flow.html — “Answers the system cannot produce”; “The board pack is rebuilt from exports every quarter”; “Planning happens outside the system, in a workbook”; “Most ERP projects do not fail on the software”; the two questions quoted above

What stays from current copy

• “Your CFO Advisor for Finance, ERP, EPM & AI-supported automation” and the paragraph under it. This is the current page's own advisory-depth section; the direction is largely an argument for promoting it to the top.
• “Our focus is not on individual tools, but on the overall picture of the financial architecture.” Kept verbatim. It is the thesis.
• The card row's system list — ERP, EPM, CRM, HCM, finance operations, AI-supported automation. Kept as the surface claim, moved up to sit under the hero.
• The named case studies as the depth evidence, with the source's own restraint: the published case studies carry no outcome figures, so none are added.
• The contact block with a named person. Kept — a page arguing that the reader should talk to people who have read the landscape has to show one.

src/data/baseline/pages/index.json e-flow.html — the five described projects and “we do not invent them”

What to judge — the one/three/thirty-second rule

• At one secondWeakest point. Nothing physical has happened. The reader meets a claim about judgement, which is slower to land than a jammed close.
• At three secondsThe verb is “crosses” and the consequence is “an answer you can defend”. Judge whether that is concrete enough to count under the rule, or whether it is still abstract.
• At thirty secondsStrongest point. Surface, method and the questions to ask any partner are all present, and the reader leaves with something usable even if they do not call.
• Hard rules to check on every lineNo promise about who stays; no claim about how many people; the word “consultants” absent. Any redraft is failed on any one of the three.