Gatik Suthar

Why this persona fits the audience

He runs the backend for a 2-person internal-tools startup in Pune that serves local SMEs with document outputs and simple workflow apps. The team currently uses free and open-source command-line converters, cron jobs, and manual testing to generate PDFs and other files for client projects.

• Age: 31
• Location: Pune, India
• Occupation: Technical cofounder
• Income: ₹24L
• Education: Bachelor's degree in computer engineering
• Company size: 2
• Years in role: 4

“The real challenge isn't building something new, it's making what you have work reliably and efficiently, especially when resources are tight.”

Gatik Suthar, 31, is a technical cofounder based in Pune, India, where he lives with his parents and younger sister. Holding a Bachelor's degree in Computer Engineering, he co-founded his internal-tools startup four years ago with a vision to empower local Small and Medium-sized Businesses (SMBs) with custom software solutions. His company, a lean two-person operation, specializes in creating document output tools and simple workflow applications. Gatik is the technical backbone, responsible for all backend development, system architecture, and deployment. His approach is deeply rooted in resourcefulness and a commitment to open-source software. He meticulously crafts solutions using a stack of free and open-source command-line utilities, cron jobs for automation, and custom Python scripts. For instance, he recently spent two weeks optimizing a document generation pipeline for a local textile exporter, integrating Pandoc for complex HTML to PDF conversions and building custom data parsers to handle their unique product catalog formats. This involved significant manual testing and iterative refinement to ensure accuracy and speed, a process he finds both demanding and rewarding. His income of ₹24L supports his family and the startup's lean operations, with personal spending focused on essential needs and occasional investments in learning resources. He views time as a critical resource, often sacrificing personal leisure to meet client deadlines and push the product forward. His decision-making is heavily influenced by pragmatism and a desire for self-reliance; he prefers to build and adapt existing tools rather than rely on expensive proprietary solutions. This philosophy extends to his personal life, where he prioritizes learning and skill development, constantly seeking ways to improve his technical expertise and the efficiency of his work. He recently decided to invest time in learning Docker and basic Kubernetes concepts, recognizing the need for more scalable deployment strategies as client demand grows, even though implementing them immediately is not feasible due to current project pressures.

Background & daily life

A day in their life

Gatik's day typically begins around 7:30 AM with a quick review of overnight logs and any urgent client emails. After a simple breakfast, he dives into coding, often tackling a specific feature request or bug fix identified the previous day. Around noon, he might have a brief sync with Rohan to discuss client progress or upcoming tasks. The afternoon is usually dedicated to deeper development work, scripting automation tasks, or researching new libraries. He often works through dinner, which is usually a shared family meal, before returning to his workstation for a few more hours of coding or system monitoring, aiming to wrap up by 11 PM. He frequently uses command-line tools to compile code, run tests, and deploy updates.

Lifestyle

Gatik lives a relatively frugal life in a joint family home in Pune, sharing a room with his younger sister. His income allows for comfortable living and contributing to household expenses, but significant savings are directed towards the startup's operational buffer. He often skips lunch to save time and money, grabbing a quick chai and vada pav instead. Weekends are a mix of intense work sessions and catching up with a small circle of college friends over board games or exploring new cafes. He prioritizes practical skills and efficient routines, viewing leisure as a necessary recharge for his demanding work.

Work life

As the technical cofounder, Gatik is the sole architect and implementer of their internal tools. His days are a constant juggle between client-specific feature development, maintaining the existing codebase, and troubleshooting production issues. He relies heavily on a curated set of open-source tools – command-line utilities for document conversion (like Pandoc), scheduled tasks via cron, and custom Python scripts for data manipulation. His cofounder handles client communication and sales, leaving Gatik to focus on the technical delivery, often working late into the night to meet tight deadlines. The pressure is constant, but the satisfaction of building functional solutions from scratch keeps him motivated.

Relationships

Gatik's closest relationships are with his family, who provide a stable home environment, and his cofounder, Rohan, with whom he shares the entrepreneurial vision and daily grind. He maintains a few close friendships from university, mostly fellow engineers who understand the pressures of the tech world. Rohan's outgoing nature complements Gatik's more reserved demeanor, and they often rely on each other's strengths to navigate client interactions and business decisions.

How they decide

Gatik is a research-heavy and pragmatic decision-maker. He thoroughly investigates available options, often experimenting with free or open-source tools first to assess their viability. He values efficiency and demonstrable results, preferring solutions that integrate well with his existing workflow and offer clear benefits without excessive complexity or cost. He’s not easily swayed by hype and tends to trust solutions that have a strong community backing or a proven track record in similar use cases.

How they sound

Gatik speaks with a measured cadence, often pausing to formulate his thoughts precisely. His language is generally formal, especially in professional contexts, but he uses technical jargon naturally. He avoids hyperbole and focuses on factual descriptions. When discussing technical challenges, he might use analogies related to plumbing or electrical systems to explain complex backend processes. He’s not one for small talk but is articulate and direct when discussing his work or technical solutions. He tends to use phrases like 'essentially,' 'the core issue is,' and 'from a practical standpoint.'