What to put above the fold when the product is hard to explain

To explain a complex product on a website, put three things above the fold: a concrete object, a one-sentence job, and a picture of the interface. Category jargon can wait. "The operating system for X" and "a platform for the future of Y" sound large, and they still leave a stranger without a picture. The first screen has to create that picture before it asks for a meeting.

You do not get a long introduction. Nielsen Norman Group's review of page visits is blunt. People often leave within 10 to 20 seconds, they read only about a quarter of the text on pages they open, and a value proposition has to land within about 10 seconds if you want a longer stay. A complex product does not get an exception. It needs a simpler entry, not a denser hero. Google's people-first guidance adds a writing test: the main heading should summarize the page and should not exaggerate. A grand category fails that test faster than a plain sentence about the job.

Start with an object

Name the thing a person could point at. A queue of leads. A schedule. A shop catalog. A drawing of a floor plan. An inbox shared by two staff. The object is the noun you would use if you were looking over a customer's shoulder.

Abstract products hide the object on purpose, because the object feels small next to the vision. Use it anyway. The vision can live further down the page, after the visitor knows what they are looking at. If you cannot name an object, you are not ready to write the homepage. You are ready to decide what the first version actually does.

Pick one object, even if the product touches several. A tool that handles intake, billing, and follow-up can still open on the intake queue if that is the daily pain. The other objects get sections of their own. Stuffing every noun into the hero is how a clear product becomes a diagram.

Say the object in the customer's language. Your internal module name is a label for the team. The homepage should say "unsigned quotes," not "the revenue workspace," if that is what people stare at on Monday.

One sentence for the job

Write the job as a sentence with a person and a result. "A clinic manager sees which recalls are due today." "A buyer compares two fabrics without leaving the product." "A founder sends a proposal that matches the last call." The sentence should be falsifiable. A visitor can tell whether your product does that.

Keep the sentence free of the category. If it still makes sense after you delete the words platform, OS, suite, and solution, you are close. If it collapses, the category was doing the work the object should have done.

Put this sentence in the heading or directly under a short brand line. Do not make the visitor assemble it from four feature chips. Chips are fine later, as a scan of what else is included. They are a poor substitute for the job, because each chip is a topic and none of them is a story.

Read the sentence to someone who knows the customer and does not know your pitch. If they say "so it is a report" and you flinch, either the sentence is pointed at the wrong object or the product is. Fix the truer one. A homepage cannot rescue a product that has not chosen a job.

Show the interface

A picture of the real interface does more for a complex product than an illustration of an idea. Crop it so the object is visible. If the job is a queue, the queue should be in the frame. If the job is a comparison, both choices should be visible. A dashboard full of equal charts tells the visitor that everything matters, which is another way of saying nothing is explained.

Use a true screen. If the product is early, use an honest prototype and say so in the caption area or nearby text, in a few words, without apology theater. A labeled sketch beats a fake screenshot of a product you do not have. Visitors who later see the real thing will remember the costume.

Show one state. The happy path is the usual choice for the hero. Empty and error states matter, and they can appear lower on the page if they teach the product. The first image should answer "what do I look at?" and not "what are all the states?"

Check the image on a phone. A wide desktop table, shrunk to a thumbnail, does not explain anything. Crop a single column or a single decision. The phone frame is part of the explanation, not a smaller copy of the board.

Where jargon can go

Jargon is not forbidden. It is badly placed when it leads. People who already live in your category want the precise term, and they should find it. Put it in the next section, after the object and the job, as a sentence like "Teams usually call this a revenue workspace. Here it means the list of quotes waiting on a reply."

That order respects both readers. The newcomer gets a picture. The expert gets the map from their vocabulary to yours. Leading with the expert term and hoping the picture arrives later loses the newcomer in the 10-second window, and it often loses the expert too, because experts have seen too many vague platforms.

A glossary page is optional and usually early. Define the one term you must use, in the paragraph where you use it. Save the glossary for when you have more than a handful of words that are genuinely yours.

Avoid a coined category you will have to explain forever. If you invent a name, the headline still needs the ordinary job next to it. The coined name can be the product name. It should not be the definition.

A short exercise

This is an exercise, not a client example.

Before: "Nimbus is the intelligence layer for modern operations." After: "Nimbus shows a warehouse lead which orders will miss today's truck." Beside it, a picture of a list with three late orders and a clear next step.

The before line has a category and a mood. The after line has an object (orders), a person (the warehouse lead), a job (see what will miss the truck), and a picture that matches. The product can still be sophisticated. The first screen does not have to perform the sophistication. It has to make the sophistication imaginable.

If your after line feels too small, check whether you are embarrassed by the actual job. The job is the reason someone pays. The homepage should be willing to say it.

What to remove from the hero

Remove the architecture diagram, the logo wall of technologies, and the paragraph about the market. Those are appendix materials. A buyer who stays will tolerate a simple "how it fits" section below. A buyer who is still decoding the object will not.

Remove a second headline that restates the category in new words. One job sentence is plenty. Remove autoplay motion that pulls the eye off the interface. The picture is the explanation. Do not compete with it.

When the sentence is the part you cannot get right, use a rewrite method before you redraw the layout. How to rewrite a homepage headline walks through audience, outcome, and contrast, with exercises labeled as exercises.

If the product is clear in the room and muddy on the page, Hanabi's design and development services are set up for that gap. The work is an interface and a site that describe the same job.