The starting scope
A visual identity and public website for a managed IT provider, with service information and clear contact paths.


Imagination.Precision.Purpose.
An independent studio · Toledo, Ohio
Our Work / PC NET TECHS Project
For PC NET TECHS, a visual identity and public website grew into a connected digital operation: an interactive brand reference and card pages, advanced SEO, Schema.org data, PageSpeed-focused delivery, first-party analytics, custom content and design controls, and PC NET DESK.
The project at a glance
The Glass City Intelligence system built PC NET TECHS. The project connects the public experience with content, design and reporting tools; the evidence below shows the delivered interface and documented capabilities.
A visual identity and public website for a managed IT provider, with service information and clear contact paths.
Astro with Wix-managed Headless content, reusable page structure, search metadata, and separate content and design controls.
The public website, brand reference and supplied interface captures. Demonstrations and protected production records have different access and data.
Website and platform implementation. It does not establish a measured increase in leads, revenue or search traffic.
Compare redesign scopes · Plan the migration · Discuss a similar project
The scope
The public site evolved from Wix Studio to an Astro implementation with Wix-managed Headless content. Search architecture, structured data, and performance work support its public reach. Behind it, PC NET DESK and the Core Console bring together a first-party analytics layer, the Website Style Engine, a custom Website Builder, reporting, workflows, and administrative controls.
The production implementation and the public demonstrations have different access and data. This page describes the built system and its documented feature surface; it does not imply a measured revenue or lead-growth result.
The public website / desktop & mobile
The luminous background, glass-like mark, typography, and interface details make the PC NET TECHS identity recognizable at a glance. Desktop and phone-width layouts are designed around their own imagery and reading space.
Maintained beyond launch
Across more than 400 GCI-reported development iterations, the public website, Core Console, and PC NET DESK have been refined through versioned changes, build checks, and live verification. Continued maintenance is part of the work itself.
The iteration count is reported by GCI. It is not a measure of business results or a service guarantee.

Six connected areas of work
A documented brand reference and interactive light and black business-card presentations, plus a Wix Studio website iteration, and an Astro public site with Wix-managed Headless content. The work covers responsive design, desktop and mobile visual backgrounds, service explanations, conversion paths, Schema.org structured data, canonical metadata, indexation, and PageSpeed-conscious delivery.
A site-owned visit log feeds the Core Console and PC NET DESK. It records page activity with timestamps, sources, device and browser context, and available approximate location and network information. Reporting groups repeat activity, surfaces journeys and engagement, and separates people from bots. Network data is contextual evidence, not proof of a person or employer.
Search strategy across services and locations, Search Console and GA4 reporting, AI crawler and AI-referred traffic analysis, service-page and geographic views, lead and conversion paths, website health, campaigns, call tracking, and competitor research. External feeds depend on their individual connections and permissions.
Visual controls for the public website, with separate styling for the Core Console and Desk. Themes, color schemes, typography, icon sets, desktop and mobile backgrounds, component sizing, per-page backgrounds, motion effects, and live previews make design changes manageable.
A structured page editor with field controls, text fitting, repeaters and nested content, section ordering, logos, and design settings. A protected draft renders against the real page for preview; publishing creates a named page snapshot. Scheduled settings and review controls support planned changes.
A desktop-style workspace and Core Console bring analytics, website controls, inquiries, tasks, approvals, calendar, reports, media, files, notifications, administrative tools, and defined agent commands into a shared operating experience.
Brand evolution / before & after
The underlying PC NET TECHS symbol remains recognizable. The earlier artwork used subdued blue and brick red with uneven overlaps and mixed lettering; the current identity uses vivid color, cleaner curves, and a more cohesive wordmark. The standalone mark now has room to work as an icon.



Slide from the earlier artwork to the current logo. The shared symbol makes the change in color, finish, and type easy to see.
Brand identity / from system to touchpoint
The public brand reference ↗ brings the supplied light and dark logo artwork, small mark, website color values, typography, usage guidance, and asset downloads together. The interactive card page ↗ presents both sides of the supplied business cards with light and black finishes, a flip interaction, and downloadable artwork.
These pages connect the identity used on the site and Desk to a tangible business touchpoint. The card images are design previews; a printer still needs to prepare final trim and bleed.



Discovery & performance / built into the site
Visibility work extends beyond a title tag. The site’s structure, structured data, crawl behavior, content, and speed all affect whether people can find and use the right page.
JSON-LD describes the business, services, and locations. FAQ data is generated from the same answers visitors see, keeping machine-readable information aligned with visible content.
Canonical metadata, an accurate sitemap for indexable pages, robots rules, and noindex boundaries help keep public service and location pages distinct from tools, drafts, and demonstrations.
Service and geographic page planning, Search Console query review, content gaps, technical SEO, and conversion-path analysis connect discoverability to useful visitor action.
Responsive image choices, selective lazy loading, deferred noncritical scripts, and mobile layout decisions aim to make the experience faster. PageSpeed and Core Web Vitals remain ongoing review targets; no specific score is claimed here.
Inside the implementation / 01
The public site sends visit events to its own reporting layer. The protected Analytics app reads that log and brings the result into both the Core Console and PC NET DESK. It is a substantive part of the system, beyond an embedded third-party dashboard.
Page paths, timestamps, referrers and campaign sources, browser and device context, engagement events, and available approximate geography and network information.
Daily and period views, top pages and sources, visitor and visit views, repeat activity, page sequences, engagement, and conversion paths. Filters distinguish human traffic, bots, public pages, and other supported scopes.
Separate AI crawler and fetcher access from visits referred by AI services. A crawler arriving at a page does not establish that a service recommended the business to a person.
GA4, Search Console, lead and call sources, campaign reporting, SEO opportunities, and competitor research provide additional views where the underlying services are connected.
Location and organization labels derive from available network data and can be incomplete or wrong. The visitor records and any associated replay links remain inside protected tools.
Inside the implementation / 02
Switch visual families, tune custom color schemes and neutrals, choose fonts and icons, set separate desktop and mobile imagery, adjust component scale, and control animated effects, pointer response, and page backgrounds. The website, Console, and Desk can have distinct appearances.
Registered fields, repeatable cards and nested content, section order, logo and design controls, and text fitting let an editor change a page without breaking its composition. Work happens in a protected draft with a rendered preview before a named page snapshot is published.
Supported website settings can be scheduled once or on a recurrence. Tasks, approvals, change history, and notifications put routine publishing work into the same workspace as the site and its measurement.
PC NET DESK / interface in context
The desktop wallpaper is part of the experience. Windows, translucent surfaces, controls, and motion effects sit over a distinctive network image. These captures come from the public Sennett trial and show its accessible controls; connected production data stays in protected tools.






PC NET DESK / Documented feature map
These module groups come from the public PC NET DESK guide. They show the breadth of the product across workspace, measurement, design, content, operations, and agent interfaces. Individual integrations and public trials have different data access and connection states.
A product within the work
The desktop-style workspace opens analytics, content, style, marketing, and operational apps in movable windows. Its companion Core Console offers conventional navigation to the same working areas, with administrative access kept separate from the public website.
The GCI-hosted interactive examples are demonstrations with browser-local data. The separate PC NET TECHS implementation contains protected, connected functions; an example shown here does not grant access to those live records.
Explore the public product guide
A connected project, maintained over time
A project may need a website, software, measurement, or a clearer way to manage information. GCI scopes the first release and the work needed to keep it useful, discoverable, and dependable as the business changes.
Start with your next idea

Tell us what you want to create or improve. We’ll help you define a useful starting point.
Start a project