Switch Automation: Powering the Transition to Digital FM

The company described as "Switch Automation: Powering the Transition to Digital FM" appears to be a single-person project focused on integrating BACnet scheduling support into a digital facilities management platform. The author states that it was built rapidly using AI tools like Codex and GPT-5.6, with an agile development approach involving customer feedback loops.

The single most important open question is: What is the actual commercial traction or adoption of this product? The description provides no evidence of revenue, customers, or market validation beyond the author's own account of building it.

This analysis is based entirely on self-reported information from the project description and author’s submission — there is no archived history, third-party verification, or independent data to corroborate any claims.

• The description states that Switch Automation integrates full BACnet scheduling support into a platform hosted on Azure Cloud.
• The UI was developed with Vue.js and the API with .NET.
• Users can view and manage building equipment schedules in one place.
• It allows facilities teams to identify performance optimization opportunities, energy savings, and bulk deployment across many buildings.

Inference Based on the description, this seems to be a software tool for managing HVAC and lighting systems within large building portfolios, using BACnet scheduling standards. However, there is no evidence of actual product delivery or usage beyond the author’s account.

• The tagline states: “Switch Automation helps teams optimize and decarbonize large building portfolios — improving operations, comfort, ROI, and reporting.”
• The project write-up claims that it centralizes scheduling data to enable quick wins for performance optimization and energy savings.
• It also positions itself as a way to deploy changes at scale by editing in bulk and sending to hundreds or thousands of buildings.
• The author emphasizes leveraging AI tools (Codex and GPT-5.6) to accelerate development, especially in unfamiliar technical domains like BACnet.

Inference The positioning is that Switch Automation is a digital FM tool aimed at optimizing building operations through centralized scheduling and automation. It frames itself as solving problems related to energy efficiency, operational control, and scalability — but this is framed only in terms of the author’s own experience and not validated by external metrics or customer feedback.

• The description states that the target users are facilities teams managing large building portfolios.
• These teams are said to be concerned with HVAC and lighting runtimes, which are managed via BACnet schedules.
• The platform is intended for use by building operators, who want better visibility and control over their systems.

Not evidenced No explicit identification of specific industries, company sizes, or decision-makers beyond the general category of "facilities teams." There is no evidence of segmentation or targeting beyond this broad description.

• The description does not mention any pricing model, subscription tiers, or monetization strategy.
• It also does not state whether Switch Automation is sold as a SaaS product, a one-time license, or offered through partnerships.
• There is no indication of how the platform generates revenue.

Not evidenced No business model or pricing information is provided in the self-reported description.

• Built with .NET, Azure Cloud, Vue.js, SQL Server, TypeScript, C#, Blazor, Visual Studio, VS Code, Nuxt.
• The author used Codex and GPT-5.6 throughout development to research concepts, break down tasks, develop components, conduct code reviews, and prepare staging deployments.
• Development followed an agile loop: Build → Test → Deploy → Engage customers → Iterate.
• The team had no prior domain knowledge of BACnet scheduling but managed to ship a functional UI and API within tight deadlines.

Inference This suggests a fast-paced, AI-assisted development process. However, there is no evidence that the product has been deployed in production or used by real clients beyond staging testing.

• The author mentions that customers actively tested the product in staging.
• The project was submitted to the OpenAI 2026 hackathon on Devpost.
• It was built rapidly, going from zero BACnet familiarity to a working solution under tight timelines.
• There is no mention of any live users, revenue, or customer adoption beyond internal testing and feedback loops.

Not evidenced No evidence of traction, such as paying customers, active usage, or measurable impact on operations or energy savings. The product remains in early-stage development according to the author's account.

• The description does not reference any competitors.
• It does not describe how Switch Automation compares to existing solutions for digital FM or BACnet scheduling.
• No mention of market size, competitive landscape, or differentiation from other platforms.

Not evidenced No competitive analysis or positioning relative to existing tools in the digital FM space is provided.

• The entire project was built by one person (Junilo Pagobo), which raises concerns about scalability and long-term maintenance.
• The use of AI tools like Codex and GPT-5.6 may introduce risks around accuracy, validation, and compliance with industry standards (e.g., BACnet).
• There is no evidence of product-market fit or commercial traction — only an author’s account of building it quickly.
• The project appears to be in a very early stage, possibly even pre-launch, based on its submission to a hackathon.

Inference The lack of commercial validation and the single-founder structure suggest high risk for investment or partnership unless further evidence emerges showing real-world use or traction.

1. Has Switch Automation been tested in any live environments beyond staging?
2. Are there any known issues with BACnet standard compliance or hardware integration?
3. What is the current stage of development? Is it ready for enterprise deployment?
4. Have you identified specific use cases or customers who are interested in adopting this platform?
5. How do you plan to scale beyond a single developer and ensure product quality and reliability?
6. Are there any partnerships or integrations with existing digital FM platforms or building management systems?