PrintVision

PrintVision runs six Solna 125 offset presses, a Heidelberg two colour, four die cutters, two precision leaflet folders, two guillotines and one automatic pasting machine out of a single building at 6/A Industrial Block, Allama Iqbal Town, Lahore. Forty-five specialists. Everything from design to dispatch under one roof.

None of that was visible from the outside. That was the whole problem.

What we inherited

The company started in 1989 as Farooq Trading Corporation, one printing machine and a founder, Ihsan Ullah Naik. A second machine two years later, then the first die. Plate making came in house through the 1990s. It became PrintVision in 2011 along with the line it still uses, we print your vision. A Heidelberg two colour arrived in 2022, flexo and gravure in 2023, an HP digital press in 2024, and in 2026 the company finished building its own ERP, every job tracked from quote to dispatch.

Thirty seven years of that, and the public face was a WordPress site running WooCommerce, Elementor and Slider Revolution, with a home page weighing roughly 200KB of HTML before a single asset loaded. We crawled it before writing anything. It had five defects worth naming, because each one became a decision:

• /shop/ returned a 404 while about forty eight demo WooCommerce products sat in the sitemap. Bird tank top. Cat bowl. Pet leash.
• The blog was live and empty.
• The stat counters rendered as broken text in the static HTML. "$1M". "0M+". "1 Person team".
• Content was duplicated twice on the purpose page, and the quote page shipped two copies of the same form markup.
• A plugin stack doing work that the page did not need.

A printer whose own website says "0M+" is not making a small presentation error. It is contradicting the one thing it sells.

The strategic call

The client wall was the unplayed card. Searle, CCL, Remington, Schazoo, SIZA. Those are pharmaceutical manufacturers, and a pharmaceutical manufacturer does not choose a packaging supplier casually, because the packaging is part of a regulated product. The old site reduced that to a logo strip near the footer.

So the positioning became one line, and it is printed on the home page in exactly these words: pharma first, never pharma only. Pharmaceutical procurement leads, and the other seven industries follow it rather than compete with it. The pharmaceutical buyer gets a dedicated page, and that page is written the way a procurement audit reads: tolerances that hold, one roof and one chain of custody, regulated-industry experience.

The voice rule underneath everything was proof over adjectives. Minimum run 50,000 outranks "high volume capability". Equipment models outrank "state of the art". Published tolerances of plus or minus 5% on colour, 1mm on size and 10 gsm on stock outrank "precision engineering".

That rule cost the client something, and they took it anyway. An early draft proposed $10M+ invested and 100+ specialists, both marked to be confirmed. The verified numbers were $1M+ and 45. The site publishes the smaller true ones. No certifications appear anywhere either, for the same reason: none had been verified at the time of writing, and a pharma supplier claiming an unverified certification has a much larger problem than a thin page.

The identity

The brand foundation was written first, twenty five sections of it: purpose, mission, vision, quality policy, core values, objectives and KPIs, audience profile, competitive analysis, SWOT, personality and tone, positioning statement, brand promise, value proposition, key brand experience, communication strategy, legal and compliance, then the visual system.

The mark is a ribbon. Read one way it is stock feeding through a press; read another it is four plates laying down in register. It is drawn flat for print and dimensional for screen, and it holds at a favicon.

The palette is the process:

• Cyan #00AEEF
• Magenta #EC008C
• Yellow #FFF200
• Key #231F20

Four colours, and each has a single-plate colourway so the mark survives one colour jobs, foil, emboss and deboss without being redrawn. Typography is Avenir Next Condensed across the full range, Ultra Light to Heavy with italics. Condensed, because a printer's copy is mostly specifications and specifications are dense.

Then the applications: stationery, ID badges, the company profile, an information-rich brochure, social templates keyed one plate colour per service line, brand artwork, an icon set, apparel and the corporate video.

The website

The new site is twelve routes, ten indexed, statically generated with the Next.js App Router. No CMS. Copy lives in typed TypeScript modules, which means every word change arrives as a reviewable diff next to the code that renders it, and derived values compute themselves rather than going stale.

The design is the identity inverted. The approved direction was a light paper system, paper #F7F5F0 on ink #161511. What shipped is the same semantic vocabulary flipped to black, #060607 paper and near-white ink, with CMYK surviving only as a hairline colour bar and plate-coloured accents, under 2% of any viewport. Full-saturation CMYK as interface colour was one of the things that made the first attempt read as generic. The cursor is a registration mark, and it turns magenta over anything interactive, except text inputs, where it hands back the native I-beam because a registration mark over an editable field breaks the affordance.

Secondary text is pinned at a contrast level that clears AAA on every surface. It is not dimmed for style.

Underneath, the site is a front door to the ERP the company already built. Both public forms POST to a single server route that calls a Supabase procedure, and the shape of that payload is a written contract between the web side and the ERP side. The four-step quote wizard is therefore not a contact form with extra fields, it is a specification intake: product, specifications, artwork, contact and review, and what comes out the other end is machine readable. The live chat answers from the ERP's own knowledge base, and talking to a person is an explicit escalation rather than the default.

Both public endpoints sit behind bot detection and per-IP rate limiting, and the privileged database call was moved server side so the ERP team can revoke the public grant without breaking the website.

Performance was treated as a content problem rather than a build flag. The plant reel was compressed from 26MB to 7.4MB, every video is poster first, and playback is deferred until scroll. Visitors who prefer reduced motion never download the video at all, they keep the poster.

Search

Fifteen articles were written and published before launch, in four categories, all shaped like queries a buyer types before they know which supplier to call. Choosing GSM for pharma cartons. Offset versus digital by run size. Pantone versus CMYK for brand colour consistency. What buyers inspect in export-quality packaging from Pakistan. How to audit a pharmaceutical packaging supplier.

The rule was written down and followed: do not launch an empty blog.

We also ran an SEO audit against our own work and published the result rather than filing it. It found H1 quality to be the systemic weakness, and three of its top five fixes shipped the same week. Two were declined on purpose, because brand voice was judged to be worth more than a keyword on those particular pages. A recommendation you decline for a stated reason is a decision. One you never write down is an accident.

What shipped

• A written brand foundation, twenty five sections
• A complete visual identity: mark, colourways, type system, icon set, brand artwork
• Stationery, company profile, brochure, social templates, apparel
• A corporate video
• A twelve-route website, statically generated, wired into the client's ERP
• A four-step specification intake replacing an email-and-hope quote form
• Fifteen search-shaped articles, live at launch
• A client portal, provisioned from the ERP and kept out of the index

Design, technology and growth were not three vendors passing files between them here. The brand foundation set the positioning, the positioning wrote the copy, the copy shaped the routes, and the routes fed a production system the client already owned. That is the argument for doing it in one team, and PrintVision is the clearest proof of it we have.