Cameron Weeks and the trouble with starting over

Bracken Fields broke Cameron Weeks’s Nikon SLR at a basketball game. As apologies go, his next move was unusually productive: he offered to help Weeks fix a hardware problem at a hotel. A damaged camera had created a small debt. Working together revealed something rather more valuable. The two discovered they made a useful team.

It is an appealingly untidy beginning for a career in communications software. There is a friendship, an accident, and a job that needs finishing. The business plan enters later. Weeks would go on to lead Sharpen and co-found Edify with Fields, spending years on a problem familiar to anyone who has explained an issue to a company, changed channels, and been invited to explain it all again.

His working life has followed that irritation through several forms: phone systems, contact-center software, customer conversations, and now the machinery of existing businesses. Along the way, he has tried giving colleagues more freedom over both their tools and their time. The recurring interest is practical. What arrangement lets people get on with the thing they came to do?

A repair job with a long afterlife

The early work was in Indianapolis. Weeks and Fields attended Purdue, and their present-day firm dates their collaboration to 2006. They worked on a custom private branch exchange, the system that handles a business’s telephone calls, for an Indianapolis high-rise. By 2008, they had left Purdue to build full-time. The undertaking grew into cloud telephony.

That route into entrepreneurship puts a customer request ahead of a market category. Somebody needed a working phone system. The engineers could see a way to make one. Such beginnings have an advantage: a real person can tell you whether the thing works. They also have a disadvantage: a real person can tell you when it does not, usually while needing it immediately.

The partnership continued through Fathom Voice, Sharpen, and Edify. The names marked changing products and ambitions, but the collaborators remained. Weeks supplied the product-driven chief executive’s perspective; Fields brought the technical leadership associated with his CTO roles. Their long association gives the story continuity that a list of company names can obscure.

When the name stopped fitting

In June 2016, Weeks Communications, doing business as Fathom Voice, became Sharpen Technologies. A company that had sold office telephone systems was moving into cloud software for managing contact centers. It could still supply the receptionist’s desk phone. Its larger concern was how sales and support teams worked around that phone.

The business then employed about 50 people and had 22,000 users. Its software helped coordinate inbound and outbound calling and supported sales cadence management: when to contact someone and what to say. The rename made a plain admission. A name containing “Voice” had become too narrow for what the company was trying to sell.

That is a useful moment in Weeks’s story because it makes his progression visible without requiring a grand conversion. The telephone stayed. Around it accumulated messaging, customer information, and the work of teams. The product was becoming a system for handling relationships, with all the organizational mess that relationships bring.

Permission to admit you need help

Weeks had an equally practical problem inside the company. He could interest people in the venture, but recruiting, developing, and retaining them required abilities he did not consider his own. Early at Sharpen, he brought in Emily Hoover, later Emily Wolfington, to run operations. Hiring someone to help build the organization was part of building the product’s future.

By 2018, he had a name for the underlying principle: “The don’t fake it rule.” A colleague who lacked a skill should be able to acknowledge the gap so someone better equipped could take over. There is a certain economy to that approach. Pretending to know an answer consumes time that could be spent finding somebody who does.

His view of delegation extended to software purchasing. Once a business had several dozen employees, he argued, the chief executive should have capable people choosing the tools for their own responsibilities. A shared reason for the company’s existence mattered more than senior management’s preference among marketing packages. For a software founder, it was an amusingly relaxed attitude toward the shopping cart.

“The don’t fake it rule.”

Cameron Weeks on acknowledging gaps in expertise

Sharpen also added experienced industry leadership. In 2017, it announced the arrival of Pam Hynes and Bill Waller, whose backgrounds included established communications vendors. Weeks’s explanation joined technology to the people supporting customers. The product needed an organization around it, one capable of helping another organization make a consequential change.

Keep the conversation together

Edify, founded in 2018, gave Weeks and Fields another chance to design the system. Its Huddle platform brought together contact-center functions, internal communications, and communications APIs. Those labels describe different software markets. For the customer, the ambition was easier to understand: move between ways of communicating while staying inside the same conversation.

Consider the experience the design addresses. A person calls, sends a photograph, or follows up with a message. Each action concerns the same unresolved task. If the company treats those actions as separate encounters, the customer becomes the courier carrying context between them. Edify’s proposition was to let the software do more of that carrying.

An early analyst assessment described Huddle allowing voice, text, email, and photographs to be combined without disconnecting. Machine learning was intended to help route interactions and improve how the work moved. The interesting unit was the journey through the service, including the employee’s access to information, rather than any single channel.

In 2019, Edify announced $10 million in seed funding led by First Round Capital. Investor and board member Bill Trenchard brought experience from LiveOps. The money was intended to expand the team and market presence. It was financing for a young business entering a field where established suppliers already had longstanding customer relationships.

Weeks’s public writing made his impatience with that field explicit. In a 2020 essay, he argued for easier cloud adoption, usage-based payment, and a common system for contact-center agents and other employees. His argument connected commercial arrangements to the product experience. Buying and operating the tools could create friction before a customer ever picked up the phone.

He also had a quieter communication philosophy. Writing about sales texting in 2016, he advised having a clear purpose, respecting boundaries, adapting to the prospect’s preferred channel, and avoiding repeated messages. More access to someone does not confer an unlimited invitation. The restraint fits a career concerned with making conversations easier.

Friday becomes an experiment

In July 2021, Weeks turned a similar question inward. Edify would pilot a four-day workweek. Offices would close on Fridays, while customer-success staff would use alternative four-day schedules to preserve round-the-clock support. Each department’s commitments to the business would remain in place.

The proposal treated the calendar as something the company could test. Weekly employee surveys would help evaluate the pilot before a decision about permanence. Outcomes and productivity would matter. That distinction gives the episode its interest: a pleasing announcement was accompanied by the less photogenic work of arranging coverage and deciding what to measure.

The announcement described a lively reaction in company chat, complete with memes, GIFs, and emojis. Even an enterprise communications platform occasionally gets to carry uncomplicated good news. Yet the published plan remained an experiment. Its value in this story lies in Weeks’s willingness to alter an established arrangement and make the operating details part of the proposal.

A workflow you could actually draw

At Enterprise Connect in 2022, Weeks demonstrated Edify’s no-code workflow tool. The demonstration prompted analyst Blair Pleasant to observe that she could create a basic workflow herself despite lacking programming skills. It is a small, concrete response to a product demonstration: somebody outside the engineering team could imagine doing the work.

The tool let users arrange customer-experience processes through drag-and-drop design. Edify also offered Workflows beyond its existing licensed customer base. That move made the workflow itself an entry point, rather than requiring every prospective user to begin by replacing an entire communications system.

Weeks argued that video, too, should be a natural part of a customer conversation. Adding it should not require another isolated tool. Across these features, the direction was consistent: give people ways to arrange a useful interaction without making them assemble the underlying software industry first.

After the launch, the repair

Avaya announced its acquisition of Edify on May 8, 2024. Its account emphasized no-code orchestration, customer journeys, workflows, and engineering talent. The transaction terms were undisclosed. By then, Tony Lama was Edify’s CEO; Weeks’s tenure in that role had ended earlier. The distinction matters in a career that has already moved into another chapter.

Today, BACK Ventures lists Weeks as managing partner and describes a technologist who still works directly in code. Its studio builds communications and AI infrastructure businesses while its operating practice works with existing companies. Fields is again a managing partner. The familiar collaboration now serves businesses that need repair as well as products being built from scratch.

For a full-year 2025 engagement, the firm reports that Weeks served as contract CEO of a telephone answering service. Its case study describes a move from monthly losses to approximately $476,000 in adjusted annual net profit, using about $35,000 in new capital. These are BACK Ventures’ figures for an unnamed client. The operational work included rebuilding financial visibility, consolidating data, and automating service delivery.

The setting brings his career back close to its beginning. Calls still have to be answered while the systems behind them are being changed. A working service cannot pause merely because its operators have found a better arrangement. Years after the hotel repair, Weeks is still occupied with the practical business of fixing something while people need to use it.