Why this persona fits the audience
Oversees a small nonprofit web stack with one part-time contractor and keeps a PHP dashboard running for donations, volunteer scheduling, and staff lookups. A lot of the workflow still moves through Excel imports, lookup tables, and a legacy admin site.
- Age: 45
- Location: Jersey City, New Jersey, USA
- Occupation: Operations analyst supporting nonprofit web systems
- Income: $98k/year
- Education: B.A. Information Systems
- Company size: nonprofit with 25 staff, 50 active volunteers
- Years in role: 8
“If it ain't broke, don't fix it – but make sure you have a backup of the manual you used to build it.”
Conrad Jacobs-Abbott has spent the better part of two decades navigating the intricate, often under-resourced, digital infrastructure of nonprofit organizations. His journey began with a B.A. in Information Systems from a state university, followed by a few years in a corporate IT support role that he found stiflingly bureaucratic and disconnected from tangible impact. Seeking a more meaningful application of his skills, he transitioned to the nonprofit sector, starting as a general IT assistant before finding his niche as an operations analyst. For the past eight years, he has been the linchpin of the web systems at an environmental advocacy group based in Jersey City. His role is less about innovation and more about diligent maintenance and data integrity. He inherited a patchwork of systems, including a custom-built PHP dashboard that handles donations, volunteer coordination, and staff directories, alongside a labyrinthine legacy admin site. His daily reality involves wrestling with Excel spreadsheets, performing manual data imports and exports, and ensuring the PHP application remains stable, often with minimal external support beyond a part-time contractor. Conrad views his work as a form of service, a quiet but essential contribution to the organization's mission. He is deeply pragmatic, understanding the severe budget constraints under which nonprofits operate. This pragmatism dictates his approach to technology: he is inherently skeptical of new, expensive solutions, preferring to optimize and maintain what already exists. His income of $98k/year, while comfortable for him living alone in his Jersey City condo, is carefully managed, with a significant portion allocated to maintaining his home and ensuring financial stability. He sees his role as a guardian of operational continuity, a bulwark against the chaos that data loss or system failure could bring to an organization reliant on its digital tools for fundraising and outreach. He recently spent three weeks painstakingly documenting the entire donation import process after a near-critical error, a task he undertook himself rather than relying on the contractor or risking staff time. This meticulous approach, while time-consuming, ensures that even the most obscure workflows are understood and can be replicated, a testament to his commitment to predictability and service.
Background & daily life
A day in their life
Conrad's day begins at 7:00 AM with his coffee ritual. By 8:30 AM, he's at his desk, reviewing overnight system logs and checking email for any urgent requests. The first few hours are dedicated to data imports, often involving complex Excel pivot tables and VLOOKUPs to merge donation records with volunteer sign-ups. He might spend an hour troubleshooting a minor bug reported by a program manager, often involving digging through old code comments or Stack Overflow archives. Lunch is a quick sandwich at his desk. The afternoon could involve a brief sync with the part-time contractor about an upcoming minor update, or meticulously updating his internal documentation for the volunteer scheduling module. He aims to wrap up by 5:00 PM, ensuring all critical data is backed up before leaving.
Lifestyle
Conrad rents a well-kept but empty-nested condo where the kitchen counter is dominated by a pour-over coffee setup and a labeled file of maintenance spreadsheets. He walks to work, passing the same bodega where he buys the same breakfast sandwich (egg, cheese on a whole wheat bagel) five days a week. Evenings are often spent reading technical manuals or local history books, occasionally trying a new coffee bean. He budgets carefully, viewing his income as a resource to maintain stability rather than a means for luxury. Social life is minimal, primarily consisting of occasional, low-key dinners with a few long-term colleagues.
Work life
Conrad is the de facto IT department for a mid-sized environmental nonprofit. His primary responsibility is keeping the PHP-based donation tracking and volunteer management system operational. This involves a lot of manual data wrangling, exporting from various sources into Excel, cleaning it up, and then importing it into the system or a related lookup database. He also manages a legacy admin site that staff use for basic lookups, which is notoriously clunky. He works closely with a part-time contractor who handles minor code updates and bug fixes, but Conrad is the gatekeeper for any significant changes, always prioritizing stability over innovation. The pressure comes from ensuring data integrity and system uptime, as the organization relies heavily on these tools for its operations and fundraising.
Relationships
Conrad has a cordial but distant relationship with his colleagues, who view him as the 'computer guy.' His closest professional confidant is the part-time contractor, though their interactions are strictly task-oriented. He maintains contact with his sister, who lives upstate, via weekly phone calls. His influence is primarily internal, focused on maintaining the operational status quo.
How they decide
Conrad is highly cautious and research-driven, preferring to exhaust all manual options and thoroughly vet any potential solution before committing resources. He prioritizes proven stability and cost-effectiveness, often delaying decisions until a problem becomes critical. He relies on documentation, peer reviews on forums, and his own extensive testing.
How they sound
Speaks in a measured, slightly monotone cadence. Uses precise, technical language but can simplify when explaining issues to non-technical staff. Avoids slang and hyperbole. Tends to preface statements with 'Well, from an operational standpoint...' or 'The data indicates...'. His tone is generally calm, even when discussing problems, conveying a sense of quiet competence.
Personality traits
- reluctant to spend on unproven tools
- territorial about his workflow
- prides himself on manual data accuracy
- slow to adopt new interfaces
- deeply loyal to underfunded organizations
- avoids unnecessary meetings
- secretly enjoys spreadsheet macros
- wary of vendor lock-in
- prefers to fix problems himself
- meticulous about documentation
Goals
- Achieve a fully automated, error-free donation processing pipeline.
- Document all existing systems and workflows comprehensively.
- Secure funding for a modest, one-time system upgrade.
- Maintain the organization's operational continuity without major disruptions.
- Develop a robust disaster recovery plan for the web systems.
Problems & frictions
- The constant need for manual data reconciliation between disparate systems.
- The aging, poorly documented legacy admin site is a frequent source of user frustration and errors.
- Limited budget for software licenses, hardware, or external development support.
- Difficulty in onboarding new staff to the existing, complex data entry procedures.
- The part-time contractor is often unavailable for urgent issues.
- Balancing system maintenance with the organization's core mission activities.
Values
- pragmatism
- service
- predictability
- stability
- duty
Interests
- database normalization
- legacy system integration
- automation
- local history
- coffee brewing
Media habits
- Substack tech newsletters
- Stack Overflow threads
- YouTube maintenance tutorials
- NPR podcasts
- Goodreads (mostly nonfiction)