← Back to projects
Client workDelivered · Live
Visit site

A corporate site for a US-registered software company, built to pass bank scrutiny during account review. One self-contained HTML file, no build step, no frameworks, hosts anywhere. Client-owned; I designed and built it.

HTMLCSSVanilla JSVercelGitHub Actions

Hyperlink Software Technology LLC


The brief

Hyperlink Software Technology LLC is a US-registered software company that needed a corporate website for an unusual primary audience: a bank reviewing its application for a business account.

That reframes the whole job. This isn't a site optimised for conversions or time-on-page. A reviewer is checking whether a company that claims to sell software looks like a company that sells software: coherent scope, real contact details, legal pages that exist, nothing that reads as a shell. Trustworthy beats trendy, and conventional beats distinctive.

This is client work. The company and the site belong to the client.


My role

Sole developer. Design and build, including the copy structure and the legal page scaffolding, plus deployment.


Key decisions

One self-contained file. index.html with inline CSS and a small amount of vanilla JavaScript. No build step, no bundler, no framework, no dependency beyond Google Fonts. The constraint was deliberate: the site has to be hostable anywhere, on short notice, by anyone, with no toolchain to reconstruct. A corporate site that a bank might check should not be one npm install away from not existing.

Conventional US software startup styling. Deep navy ground with copper accents and a serif/sans pairing. Legible, professional, unremarkable in the way this audience wants. The design brief was explicitly to be boring in the right places.

Nothing invented. A bank is going to scrutinise this, so there are no fabricated testimonials, no fake client logos, no invented statistics, and no imaginary team members. Where real details weren't available yet (registered address, legal copy), the site carries visibly bracketed placeholders and the legal pages are marked as incomplete, rather than filled with plausible-sounding text. Omitting a section is safer than inventing one.

Full declared scope, not a narrowed one. The copy, meta description, and terms all had to describe the same business: custom software engineering, security and private deployment services, and proprietary subscription-based privacy and network security products. The site names the two products, Magic VPN and Magic Private Browser, with honest status labels rather than implying either had shipped.

Careful with the name. "Hyperlink" alone is a registered trade mark held by another party, so the full company name is used throughout the site, in copy, alt text, and artwork, with "the Company" as the defined short form in legal text.


Stack

  • Site: semantic HTML with inline CSS and minimal vanilla JS, mobile-first responsive, with meta and Open Graph tags and a full favicon set.
  • Pages: index.html (hero, who we are, products, services, contact), plus privacy.html and terms.html sharing the same header, footer, and styling.
  • Deployment: Vercel, with GitHub Actions workflows for deploys.

Challenges & solutions

Routing without a framework. Vercel's cleanUrls setting broke homepage routing for a static multi-page site; removing it from vercel.json fixed the root path. The kind of problem that only exists because there's no framework papering over it, and takes one line to solve once you've found it.

Being honest about readiness without looking unfinished. The company's products aren't launched. A site-wide notice marks the site as under development, and the products carry "Coming Soon" and "Under Development" labels. For an audience assessing legitimacy, visible honesty about stage is worth more than polish that overstates it.


Status

Delivered and live. The client owns the site and the repository. Bracketed placeholders remain where the client still needs to supply registered address details and final legal copy.