Jerome Gulgowski

Why this persona fits the audience

Runs a 3-person US-based SaaS startup building internal dashboards for logistics clients. Currently generates HTML reports via Python scripts and manually hosts them on GitHub Pages or sends raw files to clients, struggling with version control and secure sharing without setting up full CI/CD pipelines.

• Age: 32
• Location: Austin, Texas, USA
• Occupation: Founder & Lead Developer
• Income: $145,000
• Education: Bachelor's in Computer Science
• Company size: 3 employees (including himself)
• Years in role: 2 years

“I spend half my life building systems to move data faster, only to realize I'm still manually moving the last mile.”

Jerome Gulgowski is a 32-year-old software engineer turned solo founder based in Austin, Texas, who embodies the archetype of the modern technical operator. Holding a Bachelor's in Computer Science, he spent five years working as a backend developer for logistics giants before launching his own venture two years ago. His startup focuses on creating custom internal dashboards for supply chain managers, a niche that demands high precision and reliability. Despite generating $145,000 in annual revenue, Jerome remains the primary architect and operator, a role that has led to a complex set of operational bottlenecks. He currently relies on a fragile ecosystem of Python scripts that generate HTML reports for clients, which he then manually uploads to GitHub Pages or emails as raw attachments. This approach, while functional, creates significant friction regarding version control and data security, forcing him to constantly choose between speed and safety. His personality reflects a high openness to new technologies but a conscientious hesitation to adopt unproven tools that might compromise stability. He is deeply invested in the open-source community and values autonomy above all, viewing his current manual processes as a temporary state of inefficiency he is desperate to eradicate. Jerome's recent decisions have centered on evaluating lightweight automation tools that do not require the heavy lifting of a full CI/CD pipeline, a constraint born from his limited budget and small team size. He is a man of few words but many lines of code, driven by a singular goal to build a scalable, secure product without sacrificing the independence that defines his entrepreneurial journey.

Background & daily life

A day in their life

Jerome wakes up at 5:30 AM for a quick workout and black coffee before diving into the day. By 7:00 AM, he is already checking logs and responding to overnight errors in the production environment. The morning block is reserved for deep work on the Python generation scripts, a task requiring intense focus. Around 11:00 AM, he switches context to manage the two remote contractors, reviewing their pull requests and providing feedback on UI components. Lunch is usually eaten at the desk while reading industry news. Afternoons are fragmented by client calls and troubleshooting ad-hoc issues, leaving him feeling drained by the end of the day. He often stays until 7:00 PM to push commits, trying to finish the manual hosting tasks before logging off to avoid burnout.

Lifestyle

Jerome lives in a converted warehouse unit in East Austin, surrounded by exposed brick and the hum of the city. His evenings are a mix of winding down with mechanical keyboard assembly projects and coding side-projects that rarely see the light of day. He is health-conscious but inconsistent, preferring gym sessions at 5 AM over late-night runs, though he often skips them when deployment deadlines loom. Financially, he is frugal yet willing to invest heavily in tools that save time, treating his cash flow as a variable to be optimized rather than hoarded. Socially, he maintains a tight circle of three or four fellow founders, meeting occasionally for coffee where the conversation inevitably drifts toward server architecture and market fit rather than gossip.

Work life

As the sole technical backbone of his logistics dashboard startup, Jerome spends 80% of his day in IDEs, wrestling with Python scripts that generate client-specific HTML reports. The remaining 20% involves client calls and managing two junior contractors who handle frontend styling. His workflow is currently a patchwork of local Git branches and manual file uploads to GitHub Pages, a process that frequently leads to version confusion and awkward moments when clients receive outdated data links. He operates in a state of constant low-level stress regarding security, ensuring that sensitive logistics data isn't inadvertently exposed through shared folders. The lack of an automated pipeline means every client update requires him to manually intervene, a bottleneck he desperately wants to solve without the overhead of a full enterprise DevOps setup.

Relationships

Jerome is married to Elena, a graphic designer who provides the creative counterbalance to his logical mindset; she manages the company's branding while he handles the backend. They have a close-knit group of friends, mostly other tech entrepreneurs in Austin, whom he relies on for peer advice. His primary professional influence is a former mentor from his college days, now a CTO at a mid-sized firm, whose advice on infrastructure he weighs heavily before making architectural decisions.

How they decide

Jerome makes decisions through a lens of rigorous cost-benefit analysis focused on long-term maintainability. He is not impulsive; he prefers to prototype solutions in isolation before committing resources. When evaluating new tools, he prioritizes security and automation capabilities over user interface polish, often skipping marketing fluff to read documentation and source code directly. He is influenced by peer validation within his technical community but ultimately trusts empirical evidence and personal testing above all else.

How they sound

His speech is precise, measured, and devoid of corporate jargon unless necessary. He speaks in complete sentences with a clear, flat cadence, often using technical metaphors to explain non-technical concepts. He avoids hyperbole and emotional language, preferring factual descriptors like 'inefficient' or 'brittle.' He rarely uses slang, maintaining a professional tone even in casual settings, though he can become animated when discussing specific engineering challenges or security vulnerabilities.