Strategic Context
I joined Bynry Corporation in September 2021 as an Assistant Marketing Manager -- the company's first dedicated marketing hire. Bynry was building SMART360, an AI-enabled utility management platform covering CIS (Customer Information Systems), billing, AMI (Advanced Metering Infrastructure), and work order management. The product was designed for water, electricity, and gas utilities looking to modernise away from legacy on-premise systems that had been in place for a decade or more.
The situation was a genuine zero-to-one challenge. No marketing function existed. No brand awareness. No inbound pipeline. The team was under 15 people, mostly engineers. I reported directly to the CEO and was responsible for everything -- positioning, content, demand generation, sales support, and campaign execution. Over the next 2.5 years (through March 2024), I grew into the Marketing Manager role with ownership of PMM and growth across both the India and US markets.
The core strategic challenge went deeper than awareness. Indian utility procurement is risk-averse and committee-driven. Government-adjacent buyers default to "the vendor we already know." Convincing them to trust a startup with critical infrastructure software required more than good messaging -- it required a fundamentally different approach to credibility-building.
The Problem
Bynry's early positioning described itself as a "cloud-based utility management platform." Technically accurate. Strategically useless. Three problems made this untenable.
First, "cloud-based" meant nothing to utility operations managers who cared about uptime and data security, not deployment architecture. Second, "utility management platform" was so broad it competed with everything from billing software to SCADA systems without differentiating on any dimension. Third, the messaging did not address the actual anxiety buyers had: what happens if this startup disappears in two years and I am stuck with a system nobody can maintain?
I ran a structured positioning exercise using April Dunford's methodology -- competitive alternatives, unique attributes, value for the customer, and the market category that makes the value obvious. This was not an academic exercise. I studied over 100 CIS and billing RFPs from government tenders to understand the language utility buyers actually used when describing their problems. I interviewed early-stage prospects and mapped the evaluation criteria that consistently appeared across procurement documents.
The Approach
The positioning pivot that worked was reframing Bynry from "another utility management tool" to something more aspirational and concrete: "Build a Digital Utility of Tomorrow." This was not a tagline pulled from thin air. "Digital transformation" was already embedded in the vocabulary of government policy documents, Smart City Mission proposals, and utility board presentations. I was aligning Bynry with a narrative decision-makers already believed in but did not have a software vendor for.
The competitive positioning shifted from feature-by-feature comparisons -- which Bynry would lose against mature products with 15 years of feature accumulation -- to two dimensions where Bynry had a genuine advantage: implementation speed and total cost of ownership. Legacy systems took 6-12 months to implement. SMART360 could go live in weeks. Legacy systems required on-premise infrastructure and dedicated IT teams. SMART360 was SaaS.
I mapped the typical buying committee across our first prospects. Technical evaluators cared about APIs, data migration, and security compliance. Operations heads cared about whether their team could use the software without extensive retraining. Procurement officers cared about government compliance and vendor stability. I built persona-specific messaging and materials for each: API documentation for the technical evaluator, workflow migration diagrams for the operations head, TCO comparisons and compliance checklists for the procurement officer.
The GTM itself combined three channels that worked together. Industry events where actual utility decision-makers attended, not vendor-to-vendor conferences. Problem-specific content -- not broad digital transformation thought leadership, but hyper-specific pieces like technical guides for migrating from specific legacy systems. And direct engagement in industry forums (WhatsApp groups, LinkedIn groups, government-organised utility forums) where I contributed genuine domain expertise before ever mentioning Bynry.
What Worked (and What Didn't)
What did not work first: cold outbound to utility email addresses scraped from government websites. Response rates were below 1%. Utility buyers do not respond to cold emails from unknown startups. The lesson was obvious in hindsight -- in a trust-deficit market, you need credibility before you ask for attention.
Generic "thought leadership" content also underperformed initially. Blog posts about utility modernisation trends were too broad, too similar to what consulting firms already published, and not specific enough to operational realities of Indian utilities.
What worked was the combination of domain credibility and specific positioning. The 100+ RFPs I studied gave me language and framing that resonated immediately with buyers because it was their own language reflected back to them. The persona-specific materials meant that every stakeholder in the buying committee received content that addressed their specific concerns and fears, not a generic pitch deck.
The industry event strategy worked because I prepared the CEO and sales team with persona-specific talk tracks and objection responses. We were not doing lead generation through booth scans. We were having substantive domain conversations that established Bynry as a credible participant in the utility technology ecosystem.
Results
Over the course of my first Bynry stint (September 2021 to March 2024), the GTM engine produced concrete outcomes. Bynry secured its first paying clients -- full commercial contracts with Indian utility organisations, not trial accounts. The positioning framework and persona-specific messaging became repeatable infrastructure that the sales team could use independently.
The broader demand generation engine I built in parallel (covered in a separate case study) generated 300+ MQLs in 9 months, grew US website traffic by 2,000%, and reduced the sales cycle from 9 months to 3 months. But the positioning and GTM framework was the foundation that made all of those results possible.
I left Bynry in March 2024 to take a role at MetaOption, but returned in July 2025 as Product Growth Lead -- a senior role that speaks to the impact of what we built. The positioning framework, the "Build a Digital Utility of Tomorrow" narrative, and the persona-specific sales architecture I created during the first stint are still the foundation of how Bynry goes to market.
What I Learned
Three things from this experience shaped how I approach every GTM challenge since. First, in trust-deficit markets, credibility precedes demand generation. You cannot generate demand from buyers who do not believe you are a legitimate participant in their industry. The RFP study and industry engagement were not optional extras -- they were prerequisites.
Second, positioning that uses the buyer's own language is exponentially more effective than positioning that tries to educate buyers on new concepts. "Build a Digital Utility of Tomorrow" worked because utility leaders were already talking about digital transformation. I gave them a vendor to attach that ambition to.
Third, the 0-1 journey in B2B SaaS is not a marketing problem or a sales problem. It is a credibility problem. Every channel, every piece of content, and every conversation needs to be evaluated through the lens of "does this make us more credible to the specific people who will sign the contract?"
Related Case Studies
Securing first clients required both strong positioning and execution infrastructure. The full GTM engine case study covers how the system that generated those first clients was built and scaled. For a pre-launch GTM framework comparison, the MetaOption GTM case study shows the same approach in a different vertical.