RC Kosačky: five sheets, a CMS catalogue, and one person behind the price
PaedDr. Eduard Drutarovský — EXPORT IMPORT
Eduard Drutarovský imports remote-controlled tracked mowers, flail mulchers, and forestry mulchers from Asia. His business has been registered in Košice since 1995; he picks and imports the machines himself and sells them direct, with no dealer margin — his prices run between €2,000 and €6,200, where the category leader starts above €33,000. Before the site he sold through classified ads on Bazoš under rotating seller names to dodge bans. That was exactly the trust gap the site had to fill: one named person, one address, one phone number. It is not an e-shop — a visitor sends an enquiry and Eduard calls back. The site is built as five separate sheets rather than one endless scroll, the machine catalogue lives in Sanity, and Eduard edits it from his phone in a purpose-built simple admin where he can add a machine, its prices, and its video. The project took 8 working days on a €300 budget.
Presentation website with a CMS catalogue and a custom admin
Project type
Enquiries for machines instead of ads under borrowed names
Main goal
€300
Project price
Selected screens and visuals
Visual project preview shows how the website looks on different devices. Responsive design ensures perfect display on mobiles, tablets and desktops.
The hero carrying “Kosím tam, kde vy chcete” — a line Eduard dictated word for word.
The non-trivial parts of the project
Sections can be built in a day. This project rested on something else: giving a name and a face to a price five times below the category leader, building a catalogue that changes daily and is managed from a phone, and putting nothing on the site that cannot be backed up.
A price five to ten times below the category leader
The known brand in this category starts above €33,000; Eduard’s machines cost €2,400 to €6,200. A gap that size is either a trust catastrophe or the entire brand. Until then he sold through classified ads under rotating seller names, so a buyer never knew who they were writing to.
We built the site around one named person rather than a “dealer network”: his name, a business registered in Košice since 1995, the company number, the address, and one phone number that he answers himself. The price is explained in a single sentence — he imports direct from the manufacturer, so there is no dealer margin in it. That is also why the full price list is published even though the competition usually hides it: here a published price is the argument, not the risk.
Technologies and implementation
A dedicated “Kto som” sheet, the company record in the CMS, JSON-LD
A catalogue that changes every day
There will be around twenty machines, and the client described the churn exactly: “one drops out, another comes in, it changes every day.” He also described how he wants the site read — “when he clicks the offer, the next page comes up” and “he clicks there and moves on”. That is two briefs at once: an architecture for reading and an architecture for upkeep.
We split the site into five separate sheets with an index on the home page — exactly the reading model the client described. The catalogue got a row per machine rather than a page per machine: twenty records in a CMS are easy to keep current, twenty standalone pages are not. The row’s dimensions come from his own brief, given in centimetres — he ran a real-estate agency for twenty years and thinks in listings per printed page. URLs from the earlier structure were permanently redirected to the anchor of the row that replaced them, so a link on his phone never lands on a 404.
Technologies and implementation
Five sheets + an index, a row per machine, permanent redirects to anchors
He manages the site from his phone, between two calls
He said it twice: “I also need to be able to edit the offers, texts, photos, video, prices myself.” A full CMS can do that, but it asks for its own account, shows document types, and has a publish step. For a man adding a machine from his phone while standing next to it, that is friction he does not need.
He got two editing surfaces that write the same documents. `/studio` is the full CMS, and all of it — labels and help texts included — is in Slovak. `/admin` is a simple editor on the same domain behind an email and password: a machine list, add, edit, delete, nothing more. Saving expires the cache immediately, so a change is live on the first reload. And if the CMS is ever unreachable, the site quietly falls back to the content stored in the repository — the visitor sees neither a blank space nor an error.
Technologies and implementation
A Slovak Sanity Studio, a custom admin, cache tags, a typed fallback
Field video is the best proof and the heaviest thing on the page
You cannot sell a machine with a photograph — the buyer needs to see it go into tall grass and up a slope. His footage, though, is shot on a phone, low-resolution, and he uploads it straight from the field. A site with twenty rows and video in every one of them could take a very long time to open on mobile data.
Video is never shown full-bleed but always inside a chamfered plate with grain — a deliberate treatment that turns a technical constraint into part of the visual language. Whatever the client uploads is re-encoded by his own browser to 1,280 px at roughly 1.4 Mbit/s before it is even sent; depending on size, the file is then routed either directly or through temporary storage. The poster frame is taken from the original clip, because no phone gallery produces one at the video’s own proportions. A clip longer than twenty seconds never autoplays in the gallery, so a visitor scrolling twenty rows downloads posters, not footage.
Technologies and implementation
In-browser re-encoding (canvas + MediaRecorder), Vercel Blob, a poster from the clip
The visual language had to come out of his own brand
The client has his own badge and wanted it on the site. He also set clear limits: definitely not a black ground, warm earthy colours, a warm green. And his reaction to the first divider was the best brief he could have given — he asked what the shapes were supposed to be. A motif you have to ask about is not doing its job.
The palette and the motif came straight out of his badge and a photograph he sent: a paper ground, green as the ink, rust as the signal. The motif became the swath — the strip a mower leaves behind in one pass, drawn as parallel hairlines at −14 degrees, where a tight pitch means uncut and an open one means cut. Anyone who has stood in a field can name it in one word. On the home page it is also operable: the index has five bands and a touch mows each of them, so navigating the site demonstrates the product itself.
Technologies and implementation
A palette from the client’s badge, the POKOS motif, an operable index
Some of the technical data could not be backed up
The supplier quote offered specs published nowhere else, including a “EURO5” emissions claim. For machines in this class that is the wrong regime — off-road engines fall under a different European regulation. On the site such a figure would look credible and be impossible to support, which in machinery sales is a risk for the client, not for us.
Every price and every spec on the site is transcribed from Eduard’s own live listings, grouped by phone number rather than by his rotating seller aliases. Data with no public source did not go on the site and is listed in the project notes together with what would be needed to add it. The emissions claim waits for a declaration of conformity. Two clips carrying a supplier watermark were excluded. The same rule governs the structured data — that is published content too, and Google reads it.
Technologies and implementation
Transcription from listings, a register of unsupported data, JSON-LD with no extra claims
Similar problems in your business? We will help you solve them with modern tech stack.
Final structure
Complete web structure designed for maximum conversion and user experience. Each page has clear purpose and optimized navigation.
Most important website sections
Each section solved specific business problem and increased conversions
An index you mow
The home sheet carries five full-width bands, one per page. Each band wears a dense hatch — uncut ground. On hover or tap the pitch opens left to right and a saturated green washes in behind it. Navigating the site is literally mowing: you touch a destination and watch the pass complete before you arrive. The five bands are not five identical cards — the offer band is the tallest and carries both the machine count and the price floor, while the enquiry band is a short rust strip that does not sweep, because it is the end of the pass.
The offer: one row per machine
Every machine gets its own row with a gallery of photos and clips, a model code, four specs, a price, and a “Mám záujem” button. The row’s dimensions come from Eduard’s own brief, given in centimetres — he ran a real-estate agency for twenty years and thinks in listings per printed page. Details sit in an expandable panel, so the row stays short and a buyer can walk the whole catalogue without ten swipes.
How it works — terrain, remote, numbers
This sheet explains where the machine makes sense: tall grass, scrub, slopes up to 60 degrees — places where a walk-behind mower or a tractor stops being safe. Real clips from the client’s own orchard illustrate it, not stock footage. The video is low-resolution, so it is never shown full-bleed but always inside a plate with grain — a deliberate treatment, not an oversight.
Who I am — a name instead of a dealer network
The sheet says exactly this: my name is Eduard Drutarovský, my Export – Import business has been registered in Košice since 1995, I choose and import the machines myself, I deal directly with the manufacturers. And, in one sentence, why the price is what it is. Below the copy stand the company name, the registration number, and the address. The section deliberately uses no display type — it is the one place on the site where a person speaks, not a poster.
An enquiry instead of a cart
The last sheet does not ask for an order but for terrain and area. Submitting hands the buyer over to WhatsApp or straight to the phone — the channels the client actually uses and can answer quickly. The “Mám záujem” button on every machine leads to the same sheet with the model already filled in.
Project stack
Frontend and design system
A paper ground instead of black — a direct client instruction. Green is the ink, rust is the signal. Three typefaces with separated roles and a weight strategy of 800 against 200, with nothing in between. Nothing is rounded; the only chamfer is 14 degrees on the bottom-left corner.
The catalogue in a CMS
Sanity is mounted inside the application itself at `/studio`, with the schema and the desk written in Slovak — it is the only editing surface the client will ever see. It manages machines, the company record, and section copy; the dataset is public because the whole catalogue is public content, so reads need no token at all.
An admin built for a phone
`/studio` is the full CMS and asks for a Sanity account. `/admin` is the same catalogue behind an email and password on this domain, with no document types and no publish step: a list, add a machine, edit, delete. Photographs are resized to 2,400 px in the browser, so every phone photo fits. Video is re-encoded in the browser to 1,280 px, and clips over the request limit route through Vercel Blob — the client is never told which road it took.
Content integrity, SEO, and compliance
Every price and every spec on the site is transcribed from Eduard’s own live listings. Several plausible-sounding specs are deliberately absent — they come from a supplier quote and are published nowhere. The “EURO5” emissions claim on the supplier sheet was left out entirely: machines in this class fall under a different regime, and without a declaration of conformity it would be a claim with no basis. The same rule governs the structured data — that is published content too.
Frontend and design system
A paper ground instead of black — a direct client instruction. Green is the ink, rust is the signal. Three typefaces with separated roles and a weight strategy of 800 against 200, with nothing in between. Nothing is rounded; the only chamfer is 14 degrees on the bottom-left corner.
The catalogue in a CMS
Sanity is mounted inside the application itself at `/studio`, with the schema and the desk written in Slovak — it is the only editing surface the client will ever see. It manages machines, the company record, and section copy; the dataset is public because the whole catalogue is public content, so reads need no token at all.
An admin built for a phone
`/studio` is the full CMS and asks for a Sanity account. `/admin` is the same catalogue behind an email and password on this domain, with no document types and no publish step: a list, add a machine, edit, delete. Photographs are resized to 2,400 px in the browser, so every phone photo fits. Video is re-encoded in the browser to 1,280 px, and clips over the request limit route through Vercel Blob — the client is never told which road it took.
Content integrity, SEO, and compliance
Every price and every spec on the site is transcribed from Eduard’s own live listings. Several plausible-sounding specs are deliberately absent — they come from a supplier quote and are published nowhere. The “EURO5” emissions claim on the supplier sheet was left out entirely: machines in this class fall under a different regime, and without a declaration of conformity it would be a claim with no basis. The same rule governs the structured data — that is published content too.
💡 Modern tech stack = fast website + easy maintenance + long-term support
Delivery process
The project ran for eight days, from 23 to 30 August 2026: two concepts and five calls with the client. Every next step was led by what he said rather than by what looked nicer to us — which is why the site landed quickly even though the brief kept sharpening through the week.
23 August
The first concept and the client brief
1 dayIn a day we built a first complete version of the site so the client would have something concrete to react to — and he reacted precisely. His four notes became the real brief: he wants his badge on the site, definitely not a black ground, warm earthy colours, and a divider nobody has to explain. Those were art-direction instructions rather than cosmetic notes, which is exactly why they were worth having on day one.
24–25 August
Art direction out of his badge
2 daysThe palette came straight out of the client’s badge and a photograph he sent: a paper ground, green as the ink, rust as the signal. A swath replaced the divider — the strip left by one pass of a mower, a thing anyone who has stood in a field can name. This phase also produced the first catalogue design, and with it the question of how many machines it would eventually hold.
26 August
The call that set the architecture
1 dayThe call produced the two numbers that decided how the site is built: there will be about twenty machines and they change daily. He also described how he wants it read — “when he clicks the offer, the next page comes up” and “he clicks there and moves on”. So the site was built on five sheets with an index, and the catalogue on a row per machine rather than a page per machine; earlier URLs got permanent redirects. That same day the cutting-width charts left the offer as information the customer does not need, and the 4 MB video limit was lifted.
27–28 August
The CMS, the custom admin, and the colour
2 daysWe shipped Sanity with a studio entirely in Slovak, and alongside it the simple `/admin` so the client would not need a second account. He asked for a stronger green — so we split it into a text green that has to clear contrast and a fill green that may only flood areas, and recomputed every contrast ratio by script instead of estimating. Since then, saving in the admin expires the cache immediately, so a change is live on the first reload.
29–30 August
Enquiry, verification, and handover
2 daysWe finished the enquiry flow and the admin so that nothing can disappear on the client quietly: a form error appears where he is looking, and every refused save states its reason. Finally we documented how he can verify for himself that an enquiry actually arrived, without depending on anyone. The site was handed over on 30 August and went live at rc-kosacky-slovensko.sk.
Project FAQ
Do you sell machinery, or anything people do not buy with one click?
We build sites that say who you are and why your price is what it is — with a catalogue you manage yourself from your phone, and an enquiry flow that actually reaches you. Prices and specs only where you can back them up.
Leave your contact (email or phone is enough)
✨ A CMS catalogue • Managed from a phone • No invented specs