Startup.com (2001)

Executive Summary

The documentary follows govWorks.com, a startup aiming to put local-government services online. Its initial pitch centered on enabling residents to handle tasks such as paying parking tickets, taxes, and other municipal charges through one website. The founders saw a large, underserved market and believed speed and first-mover advantage would matter.

The company raised substantial venture funding and launched its site, but struggled to turn its vision into a reliable product and a viable operating business. Internal disagreements over strategy, product scope, technology leadership, and founder authority intensified as the company faced weak revenue, long municipal sales cycles, complex implementations, and a site that employees considered inferior to competitors’. The film presents these as central business-execution problems, alongside a serious breakdown in the founders’ relationship.

Strategy, Product, and Market

• Business concept: govWorks was presented as an online portal connecting local governments with residents, making government processes and payments easier to complete.
• Initial wedge: Parking-ticket payments were a concrete entry point. The founders also discussed other possible services, such as digitizing and delivering building plans, but disagreed about whether exploring such ideas showed useful breadth or a lack of focus.
• Market sizing in the pitch: Founders cited a local-government vertical market of roughly $586 billion, later described as about $600 billion or $700 billion. They also estimated New York City parking tickets alone represented about a $500 million market. These were claims made in the film, not independently verified figures.
• Competitive thesis: The team believed the market could support a few major players and that moving quickly could secure first-mover advantage. Competitors mentioned included Sidewalk.com, CitySearch, and EZgov.
• Product-scope tension: The founders debated who had authority over product strategy and how broad the service should be. Investors urged the company to focus and recognized that the founders could not pursue every opportunity at once.
• Launch and quality: The team worked through a demanding weekend to test and launch the site. But its “Ask” feature returned irrelevant results—for example, interpreting “parking” or “speeding tickets” as names—and employees called it an embarrassment. Later, the CEO acknowledged that govWorks’ site was behind competitors’ sites.

Fundraising, Ownership, and Governance

• The company pursued venture financing from firms including Kleiner Perkins, Highland Capital, and Mayfield.
• Highland put forward a term sheet for up to $17 million. The founders debated valuation, dilution, board composition, options, and investor control, with limited legal support initially available during negotiations.
• The film later cites a financing close of about $18.4 million and describes the company as having raised almost $20 million. A media interview references a $15 million Mayfield investment and a company valuation just under $50 million.
• At one point, the company was described as having raised $50 million and seeking another $100 million; elsewhere, the CEO discussed trying to raise $200 million at a very high valuation. These figures appear at different points in the film and are not necessarily directly comparable.
• A disagreement over buying out minority founders became a major financing obstacle. The proposed buyout figure for Chieh shifted from roughly $400,000–$500,000 to a settlement discussed at $700,000, with the founders considering paying personally. The dispute illustrates how early ownership arrangements and unresolved founder expectations can become costly governance issues.
• Investors sought greater influence over company strategy and leadership as the business struggled. The film shows tension between founder control and the need for experienced management and clearer accountability.

Operations and Organizational Execution

• Revenue and cash were the core operating concerns. Later in the film, management identifies flat revenue, bloated infrastructure, a longer-than-expected sales cycle, more complex implementation processes, and no clear path to cash.
• Selling to municipalities required more than a website: the company needed to collect credit-card, electronic-check, and debit-card payments, capture transaction data, and pass it to municipal partners.
• The team struggled to establish clear decision rights. Tom described himself and Kaleil as effectively acting like co-CEOs, while others expected a more formal structure. Disagreement over technology leadership and product priorities made it difficult to execute consistently.
• Employees said they needed clear, specific priorities rather than broad instructions such as “make the site fantastic.” At the same time, they worried that changing direction or rebuilding from scratch would waste time.
• The company’s intense work culture—long hours, overnight work, and weekend pushes—helped deliver a launch but also contributed to personal strain and conflict. The film suggests that sustained effort alone could not compensate for weak product quality, unclear ownership, and operational issues.

Leadership, Marketing, and Risk

• One company, one message: A key conflict arose when founders gave different strategic messages to investors. The team recognized that public disagreement could undermine credibility, even while internal debate remained necessary.
• PR and momentum: The founders used media appearances, public events, political connections, and energetic internal rallies to build visibility and enthusiasm around the mission. These efforts supported the brand narrative but did not resolve product and revenue challenges.
• Competitive response: govWorks hosted a visit from EZgov’s chairman, Brian Mundy. The visit was treated as a way to learn about a competitor, but also created internal concern that the rival was following govWorks’ language and ideas.
• Security incident: A break-in involved a stolen computer and missing files. Staff suspected targeted information gathering and worried that attackers could disrupt or redirect the website. The company responded by tightening access controls and requiring identification at the office.
• Founder separation: As the board considered consolidating leadership under one CEO, Tom was asked to take leave and later left the company. The departure involved employment terms, legal advice, and security measures, and badly damaged a long-standing personal relationship. The case shows how unclear authority and founder conflict can become operational and organizational crises.

Frameworks and Practical Lessons

• Focus the product scope: Choose a clear initial use case, such as parking-ticket payments, and prioritize it over attractive but distracting adjacent ideas.
• Use measurable launch gates: Define what must work before going live—payment processing, data capture, municipal handoff, and reliable search or “Ask” functionality—and test those requirements against real user tasks.
• Align leadership before external meetings: Debate strategy internally, clarify what is decided versus exploratory, and present a consistent position to investors, employees, and partners.
• Set decision rights early: Specify who owns product strategy, technology execution, financing, and personnel decisions—particularly when founders have overlapping roles.
• Tie spending and hiring to revenue milestones: Monitor revenue, infrastructure costs, sales-cycle length, implementation effort, and cash conversion rather than relying primarily on market-size claims or fundraising momentum.
• Treat fundraising as governance, not just cash: Understand valuation, dilution, board control, investor involvement, and legal terms before committing; secure appropriate counsel for major transactions.
• Protect founder and employee relationships with clear agreements: Establish ownership, vesting, buyout terms, and departure procedures early, before a financing or leadership dispute raises the stakes.
• Build security into operations: Restrict access to sensitive systems and files, maintain security procedures, and plan for incidents that could threaten service reliability or customer trust.

Key Metrics and Milestones Cited

Metric or milestone Figure stated in the film Local-government market estimates About $586B, later described as $600B–$700B New York City parking-ticket market estimate About $500M Highland term sheet Up to $17M Financing close / round references $18.4M, about $18.5M, and “almost $20M” Mayfield investment mentioned in media interview $15M Company valuation cited Just under $50M Further fundraising ambitions mentioned $100M and, separately, $200M IPO prediction made by an associate In six months; presented as a prediction, not an achieved outcome Later operating condition Flat revenue, long sales cycles, complex implementations, and no clear path to cash

Presenters and Sources

The film has no single formal presenter. Its principal on-camera sources are govWorks cofounders Kaleil Isaza Tuzman and Tom Herman, along with employees and associates including Chieh, Jose, David Carmel, and Vassoo; competitor EZgov chairman Brian Mundy; former Atlanta mayor and board member Maynard Jackson; and venture, legal, and board figures including Bob Higgins and attorney Isaac.

The documentary also includes Richard Herman, Ani (Kaleil’s mother), Dora, and unnamed television and media interviewers, including a Digital Jam host.