SaniCONNECT Private Franchise Collaboration Platform
A private community I led from need to launch and ongoing administration. Built on WordPress in about two months, customized and branded for SaniGLAZE, and launched in Spring 2024 to the franchise network, technicians, sales members, and corporate leadership, with more than 40 members on desktop, tablet, mobile, and companion apps.
At a glance
- Full title
- SaniCONNECT: Private Franchise Collaboration & Knowledge-Sharing Platform
- Organization served
- SaniGLAZE International
- Members
- More than 40: franchise members, technicians, sales members, and the corporate team and leadership
- Category
- Business Systems · Franchise Enablement · Internal Collaboration · Knowledge Sharing · Platform Customization
- Project type
- Private internal community · Not a public website
- My role
- Led the project end to end: need, requirements, platform selection, configuration, customization and design, rollout, and ongoing administration
- Build time
- About two months
- Launched
- Spring 2024
- Platform foundation
- WordPress (existing open-source software)
- Customization
- SaniGLAZE branding and colors, layout, custom pages, plugins, and code
- Hosting
- SaniGLAZE's server
- Access
- Desktop, tablet, and mobile devices, plus companion apps on the Apple App Store and Google Play
- Current status
- Not verified; described in the past tense
- Last updated
- October 27, 2026
Source: Project description by William A. Atkins
Executive Summary
Section titled “Executive Summary”SaniCONNECT was a private collaboration platform I planned, built, launched, and administered for SaniGLAZE International. It gave the whole SaniGLAZE community (franchise members, technicians, sales members, and the corporate team and leadership) one private place to share before-and-after project photographs, exchange practical tips and field experience, work through technical questions, and talk shop, outside of public social networks. I built it on WordPress in about two months, customized and branded it for SaniGLAZE, hosted it on the company’s server, and launched it in Spring 2024. It grew to more than 40 members, who reached it on desktop, tablet, and mobile devices and through companion apps on the Apple App Store and Google Play.
Internal platform, public write-up
SaniCONNECT was built for the SaniGLAZE organization’s internal community. It was never a public website. The original platform and its hosting environment are no longer accessible to me, so there are no screenshots here, and no addresses, login pages, member information, or franchise communications appear on this page.
This case study describes my work at a functional level. Proprietary data, credentials, and confidential implementation details are excluded.
Business Context
Section titled “Business Context”Why a franchise organization benefits from its own community. A franchise network depends on practical knowledge held by the people doing the work. Owners, technicians, and sales staff in different territories run into similar jobs, surfaces, materials, and customer situations, and what one location learns can help another. Corporate teams need a way to stay close to that experience and support it.
Public social networks such as LinkedIn are built for public, professional audiences. They are not the right setting for every internal business discussion, particularly technical troubleshooting, proprietary processes, internal operating practices, and franchise-specific knowledge.
What SaniCONNECT addressed. I identified the need for a dedicated environment where everyone in the SaniGLAZE organization could interact and share relevant information on a platform built for their business community. It was for internal communication and knowledge exchange, not a public-facing marketing website.
This page does not describe specific problems with earlier communication methods, adoption barriers, or costs, because none are documented.
The Challenge
Section titled “The Challenge”SaniGLAZE’s franchise members, technicians, sales members, and corporate team needed an organization-specific place to:
- Share before-and-after photographs of completed projects.
- Exchange tips, tricks, and practical experience.
- Raise and discuss technical questions and troubleshooting.
- Share relevant operational knowledge.
- Take part in general internal conversation.
The requirement was a private community designed for this audience: one that reflected the SaniGLAZE identity, worked on the devices people use, and kept internal knowledge in an internal setting.
The Solution
Section titled “The Solution”I chose to adapt an established community platform rather than build social software from scratch, then shaped it around SaniGLAZE.
| Element | What it was |
|---|---|
| Foundation | WordPress, extended into a private community platform |
| Customization | SaniGLAZE branding and colors, layout, custom pages, plugins, and code |
| Hosting | SaniGLAZE’s server |
| Access | Desktop computers, tablets, and mobile devices |
| Companion apps | Available through the Apple App Store and Google Play |
| Build time | About two months |
| Launch | Spring 2024, to the entire franchise network, technicians, sales members, and the corporate team and leadership |
The value was in the fit, not the invention. WordPress is existing software. My work was deciding the organization needed its own private community, choosing the platform, and configuring, customizing, launching, and running it for SaniGLAZE’s people.
Functional view drawn from my description of the platform. It shows who SaniCONNECT served and how they reached it, not its internal configuration.
Core Capabilities
Section titled “Core Capabilities”Platform characteristics
Section titled “Platform characteristics”- A private, organization-specific community for SaniGLAZE’s internal audience.
- Customized with SaniGLAZE branding and colors, a tailored layout, custom pages, plugins, and code.
- Accessible on desktop, tablet, and mobile devices.
- Companion applications available on the Apple App Store and Google Play.
- Hosted on SaniGLAZE’s server.
What it was for
Section titled “What it was for”- Sharing before-and-after project photographs.
- Exchanging tips, tricks, and practical experience.
- Discussing technical questions and troubleshooting.
- Sharing relevant operational knowledge.
- General internal conversation across franchise, sales, and corporate participants.
Franchise members, technicians, sales members, and the corporate team and leadership all used the platform across the features it offered.
Feature list not published
Community platforms of this kind can offer features such as groups, direct messaging, forums, member directories, and notifications. The specific features enabled in SaniCONNECT, and the names of the plugins and the custom code used, are not listed on this page.
My Role and Contributions
Section titled “My Role and Contributions”I led SaniCONNECT from start to finish:
- Identified the need for a dedicated, private collaboration platform for the SaniGLAZE community.
- Defined the business requirements and the intended users: franchise members, technicians, sales members, and the corporate team and leadership.
- Selected the platform: WordPress.
- Configured and customized it: branding and colors, layout, custom pages, plugins, and code.
- Owned the visual identity and user experience so the community felt like SaniGLAZE’s own.
- Built it in about two months and led the rollout in Spring 2024 to the entire franchise network, technicians, sales members, and corporate leadership.
- Managed ongoing content, adoption, and administration after launch.
This was a platform project, not an AI project. OpenAI Codex was not used on SaniCONNECT; I did the work directly in WordPress.
Technology and Architecture
Section titled “Technology and Architecture”| Component | Role |
|---|---|
| WordPress | Content management foundation |
| Plugins and custom code | Extended and tailored the platform for SaniGLAZE (specifics not published) |
| Custom pages, layout, branding, and colors | The SaniGLAZE look and structure |
| SaniGLAZE’s server | Where the platform was hosted |
| Desktop, tablet, and mobile access | How members reached the platform in a browser |
| Companion apps (Apple App Store, Google Play) | Mobile access through the app stores |
Platform versus project work. WordPress is existing open-source software and was not developed as part of this project. My work was selecting it, then configuring, customizing, extending, launching, and administering it as SaniCONNECT. The platform and its apps carried no third-party platform branding. The companion apps were available through the app stores. How they were produced and published is not documented here, and no claim is made that native iOS or Android apps were built from scratch.
Not published: WordPress version, theme and plugin names, the custom code itself, the hosting provider and server configuration, the database, the sign-in method, user roles and permissions, security measures, backups, and the app build and publishing process.
Business Impact
Section titled “Business Impact”Demonstrated:
- Built in about two months and launched in Spring 2024.
- Rolled out to the entire SaniGLAZE franchise network, technicians, sales members, and the corporate team and leadership.
- Reached more than 40 members.
- Used by every one of those groups across the features the platform offered.
What it was designed to deliver:
- A dedicated internal communication environment for the SaniGLAZE community.
- A place for franchise members, technicians, and sales members to exchange practical knowledge.
- An easier way to share examples of completed work.
- Technical discussion and peer-to-peer problem-solving.
- A digital environment tailored to SaniGLAZE rather than a generic public network.
- Collaboration across franchise, sales, and corporate participants.
- Mobile reach through the companion applications.
Membership confirmed, deeper metrics not measured
The launch date, the audience, and the membership of more than 40 are my confirmation. No engagement statistics, support-request changes, productivity changes, revenue, cost, or return-on-investment results are available, and none are claimed.
Suggested Evaluation Metrics — Historical Results Unavailable
Section titled “Suggested Evaluation Metrics — Historical Results Unavailable”Beyond membership, these are the measures that would show how much value a platform like SaniCONNECT delivers. They are listed to show how the project could be evaluated further. They are not results, and no values are implied.
| Metric | What it would show |
|---|---|
| Active users, by month | Whether members keep coming back |
| Monthly participation rate | Active users as a share of registered members |
| Posts, comments, and discussions per month | Overall activity |
| Participation across franchise locations | Whether the whole network takes part, not a few locations |
| Frequency of shared technical solutions | Whether troubleshooting questions get useful answers |
| Before-and-after photo posts per month | Whether completed work is being shared |
| Mobile app usage | Whether the companion apps reach field users |
| User feedback | How members rate the platform for collaboration and knowledge sharing |
Technical and Strategic Considerations
Section titled “Technical and Strategic Considerations”These are general considerations for any internal franchise community, drawn from the kind of work SaniCONNECT involved. They are not a record of specific lessons documented during the project.
- Participation is the product. A private community only has value if people post. Seeded content, visible corporate participation, and an easy first post matter more than features.
- Privacy is a promise to the members. Internal discussion only works if members trust who can see their posts. Clear access rules, and clear guidance on what not to post, such as customer personal data, support that trust.
- Knowledge has to be findable later. Conversation feeds move fast. A good troubleshooting answer is most valuable when it is pinned, tagged, or copied into a reference area where the next person can find it.
- Mobile access fits field work. Technicians and sales members work away from a desk. Mobile and app access put the community where the work happens.
- Customization creates upkeep. Each custom page, plugin, code change, and app release adds maintenance. WordPress, plugins, and app listings all need updates, and someone has to own them.
- Administration is ongoing. Approving members, removing departed users, moderating content, and keeping the platform current are continuing responsibilities, not launch tasks.
What This Project Demonstrates
Section titled “What This Project Demonstrates”- End-to-end ownership. Identifying the need, defining requirements, choosing the platform, building, launching, and running it, as one accountable owner.
- Franchise enablement. Giving a distributed franchise network’s practical knowledge a private home of its own.
- Platform judgment. Meeting the need by adapting established software rather than building social software from scratch, and delivering it in about two months.
- Fit to the organization. A community branded, laid out, and extended for SaniGLAZE and its audience, not a generic network.
- Adoption across the whole organization. A rollout that reached franchise members, technicians, sales members, and corporate leadership, with more than 40 members.
- Reach to the field. Desktop, tablet, mobile, and companion app access for a workforce that is often away from a desk.
Project Status and Verification Notes
Section titled “Project Status and Verification Notes”- SaniCONNECT was an internal platform for the SaniGLAZE community, launched in Spring 2024. It was not a public website.
- The original platform, its configuration, and its hosting environment are no longer accessible to me.
- Its current operating status has not been verified, and this page does not describe it as active.
- No screenshots, internal URLs, login pages, member information, or franchise communications are published.
- Not documented here: the specific community features enabled, plugin names, the custom code, how the companion apps were produced and published, and engagement data beyond membership.
- I chose to name SaniGLAZE International and SaniCONNECT on this page. This case study is my own account and is not endorsed by SaniGLAZE International. No SaniGLAZE branding assets are reproduced.
Portfolio Summary
Section titled “Portfolio Summary”SaniCONNECT is an example of business-led digital transformation in a franchise network. I identified the need for a private, SaniGLAZE-specific community, chose WordPress, customized it with SaniGLAZE branding, layout, custom pages, plugins, and code, and launched the platform in Spring 2024 after about two months of work. It reached more than 40 members across the franchise network, technicians, sales, and corporate leadership, on desktop, tablet, mobile, and companion apps, and I administered it after launch.
Related SaniGLAZE Work
Section titled “Related SaniGLAZE Work”- SaniGLAZE Franchise Media Asset Library: a Codex-built internal application giving franchise members self-service access to corporate marketing assets.
- SaniGLAZE Web Privacy & Tracking Audit Platform: a Codex-built auditing application for trackers, cookies, and consent-related concerns on corporate web properties.
- SaniGLAZE Video End-Slide Generator: a Codex-built self-service tool for localized franchise marketing video.
- SaniGLAZE Opportunity Map and SaniGLAZE Trade Show Map: business-systems dashboards for the same organization.
Changelog
Section titled “Changelog”Removed all mentions of the third-party community plugin at William's request; the platform was never branded with or presented under that name. WordPress remains the named foundation. Diagram updated to match.
Rollback: Revert the commit that made this change.
Added William's confirmed answers: he led the project end to end (need, requirements, platform selection, configuration, customization and design, rollout, administration); customization covered branding and colors, layout, custom pages, plugins, and code; built in about two months and launched in Spring 2024 to the franchise network, technicians, sales members, and corporate leadership; more than 40 members, with every group using the platform's features. Corrected the development approach: OpenAI Codex was not used. Updated the diagram to match.
Rollback: Revert the commit that added these answers.
Case study first published from William's description of the platform, following the Signal & Systems documentation standard: confirmed facts only, intended use cases labeled as intended, no metrics, versions, plugins, hosting details, screenshots, or addresses, and role details held until confirmed. Added a functional view diagram and cross-links to the other SaniGLAZE pages.
Rollback: Revert the commit that added this page.