Bengaluru · Business Operations & Founder's Office

I turn messy operations into systems that run without me.

Operator who builds. Nine years turning chaos — comms, finance, delivery, whole conferences — into automated systems that scale.

See the work Hire me / résumé
9+years, 5 promotions
600faculty run solo
20+team led
0→1ops built from zero
How I work

The same three moves, whether it's a startup or a conference.

Move 01 — Diagnose

Find the real mess

Map how the work actually flows today — the manual steps, the spreadsheets held together by hope, the thing everyone dreads. Name the bottleneck precisely.

Move 02 — Build

Build the system

Design the process, then automate it — scripts, pipelines, playbooks. Not slideware about the system: the working system itself.

Move 03 — Hand off

Make it run without me

Document it, version it, make it a single source of truth. Success is when the thing keeps working after I step back.

Selected work

Three times I took something chaotic and made it a system.

Conference technology

Ran an international conference's entire tech function — solo

AORA-GARC APSA 2026
~600 faculty · Coimbatore
Role: sole tech & ops owner
The mess

An international medical conference with ~600 faculty. A 36-page agenda locked inside a CorelDRAW-exported PDF. Registrations split between a ticketing platform and a master tracker. Faculty emails sent one by one. Certificates to generate and route by hand. No tech team — just me.

The system

Built the whole tech function from scratch: bulk faculty comms via the Gmail API + Apps Script; a Python/PyMuPDF pipeline that split certificate PDFs and pulled names by OCR; a clean reconciliation between the ticketing platform and the master tracker; 53 branded run-of-show decks generated from the parsed agenda; a Selenium WhatsApp workflow; live website management, including a mid-event hosting-suspension I escalated and resolved.

The result

A four-day, multi-hall conference run on systems one person could operate.~600 faculty reached without manual sends; certificates produced and distributed at scale; registrations reconciled cleanly.

Google Apps ScriptGmail APIPythonPyMuPDFOCRSeleniumWordPressGoogle Sheets
Founder's Office

Built the operational backbone for two startups from zero

California Software Co.
20+ person org · 2024–26
Role: GM, Founder's Office
The mess

Two early-stage startups with no operational spine. Finance, HR, QA and vendor processes living in people's heads. Static SOPs going stale. Payroll and reporting done by hand. Vendors chosen ad hoc, one crisis at a time.

The system

Built the ops function end-to-end: versioned, company-wide playbooks replacing static SOPs; automated payroll, approvals and finance reporting; quarterly KPI and budget-control loops; a unified weekly leadership report; structured vendor evaluation across KYC, payments and logistics; daily scrum as Scrum Master across product, engineering and delivery.

The result

A 20+ person org running on documented, automated systems — a single source of truth.Founders freed to focus on product and growth. For Siru: drove product ops, vendor selection and DPDP-compliant documentation.

Apps Script / SheetsPlaybook governanceVendor due diligenceScrum / AgileKPI & budget loops
Product · in progress

Turning conference operations into reusable software

Prezantim (rebrand)
2026 · building now
Role: building it
The mess

Every conference reinvents the same wheel — websites, registration, badges, comms, run-of-show, certificates — mostly by hand, mostly from scratch, every single time. The operational knowledge evaporates after each event.

The system

I'm packaging the stack I built for AORA into reusable software — event websites, registration systems and attendee apps — so the next conference starts at 80%, not zero. Productizing hard-won operational knowledge into leverage.

Where it's headed

A repeatable conference-technology platform.Early stage — this is where my operator work becomes a product. The through-line from everything above: build the system once, run it many times.

WebRegistrationAttendee appsFigmaAutomation
About

Nine years, five promotions, two worlds.

I spent seven years as an embedded software engineer for global automotive OEMs — Bosch, Vitesco, Tessolve — learning to own production software under real rigor (ASPICE, V-model) for customers across three continents.

Then I moved into operations: Founder's Office mandates, building the systems that let startups actually run — and now the technology behind conferences. The through-line never changed: take something messy and technical, and make it work reliably at scale.

What's rare about the combination is that I can build the automation myself and own the business outcome around it. Most operators can't write the code; most engineers don't want to own the outcome. I do both.

2026 →Conference Tech & Ops · Prezantim (building the product)
2024–26General Manager, Founder's Office · California Software Co.
2024Sr. System Software Engineer 2 · Tessolve
2022–24Lead Engineer · Vitesco Technologies
2020–22Senior Software Engineer · Bosch
2017–19Programmer Analyst · Cognizant
Contact

Two ways to work with me.

For hiring teams

Ops, strategy, or a founder's office

I'm looking for senior operator roles — Chief of Staff, Business Operations, Founder's Office — where I can build systems and own outcomes.

Email me Download résumé
For event teams

Running a conference or event?

I build the technology and operations layer end-to-end — registration, comms, run-of-show, certificates, the works. So you start at 80%, not zero.

Start a conversation
Reach me workwithsyam@gmail.com linkedin.com/in/syamsundarsk Bengaluru, India