Tina Parish

Calendar ownership means time allocation, not scheduling. I take the discretion, protect the blocks, decline on your behalf, and reorder priorities without asking permission every time. The goal is a calendar that matches your stated priorities — and an inbox, a travel plan, and a meeting queue that never require your attention twice.

• Complex, multi-time-zone calendar management with real decision authority over access and sequencing
• Inbox triage, drafting and sending on behalf of, and delegated-access management
• Travel booking, itineraries, contingency planning, real-time rebooking, and expense reconciliation
• Meeting infrastructure end to end: logistics, materials, minutes, and the follow-up list that actually gets closed
• Protection of attention and energy, not just calendar slots — sequencing, buffer, and recovery time built in deliberately
• Anticipation as the standard: the pre-read assembled before it is requested, the later flight held before the meeting runs long

Nothing decided in a room dies in that room. I install the operating rhythm, keep the goals and numbers honest, frame the decisions in front of you, and chase every commitment to closure. You decide. I make deciding faster, better informed, and far less expensive.

• Operating cadence: weekly leadership meetings, monthly reviews, quarterly and annual planning — agendas, pre-reads, decision logs, follow-through
• Goal and metric systems: building the scorecard, verifying the numbers are trustworthy, keeping them visible between quarters
• Decision support: framing, options, tradeoffs, and a clear recommendation delivered without spin
• Communication architecture: all-hands content, company updates, board and investor materials, sensitive internal messaging
• Orphan projects — the important work with no owner: system implementations, integrations, compliance issues, new initiatives
• Interim function leadership when a seat is unfilled, run properly until it is hired and handed off cleanly
• Board and investor support: meeting logistics, materials, minutes, updates, and data room upkeep

Most leaders under 200 people do not need two hires. They need one person who can sit in a strategy conversation on Tuesday and personally rebuild the vendor filing system on Wednesday — and treat both as equally worth doing well.

• I argue in private and align in public. You get honest pushback behind the door and zero visible daylight in front of the team.
• I tell you what is true, not what is comfortable. Leaders get insulated faster than anyone expects, and my job is to keep the signal clean in both directions.
• I do not decide, and I do not gatekeep the team. I inform, I execute, and I make sure the right people reach you at the right time.
• I hold confidentiality absolutely. Compensation, terminations, legal matters, financials, personal matters — I have handled all of it, and it stays with me.
• I become the institutional memory. The vendor's name, the terms of the contract signed three years ago, and why the last offsite went sideways.

Working inside a multi-enterprise organization spanning software and AI development, technology consulting, and e-commerce, I build the operational tooling that would otherwise sit in a backlog waiting for engineering time.

• Executive dashboards that pull scattered data into a single view a founder can actually read in ninety seconds
• Internal apps and lightweight tools for tracking initiatives, pipelines, onboarding, and recurring reporting
• Workflow automations that remove the repetitive administrative layer from meetings, follow-ups, intake, and handoffs
• AI assistants and agents configured for specific business functions — research, drafting, summarization, document review, data cleanup
• Documentation systems where SOPs are written once, then turned into the automation or prompt that runs them
• Prompt and system design so the tools stay usable by the team after I hand them over

• Capacity without headcount. Work that would justify another hire gets absorbed into a system instead.
• Faster, better decisions. Reporting that used to take a week of assembly becomes a live view, so decisions stop waiting on data.
• Continuity that does not depend on me. Documented, automated processes mean the organization keeps running when any one person is out — including me.
• Adoption, not shelfware. I build for the people who will actually use it, then train them and stay available while it sticks.
• Judgment about where AI does not belong. Sensitive communications, confidential matters, and relationship work stay human.

• Days 1–30 — Learn obsessively. Your communication style, decision triggers, priorities, pet peeves, and stakeholder map, all written down. Every leader, every recurring meeting, every number that matters.
• By Day 30 — Full calendar authority. Time allocation moves to me, with agreed rules for what gets declined, protected, and escalated.
• Fix one visibly broken thing, completely. Credibility is bought with delivery, not diagnosis. I pick the thing that is costing you most and close it out.
• By Day 60 — Take the inbox. Triage, drafting, and sending on your behalf, with the judgment calls already calibrated.
• By Day 90 — Install the cadence and the documentation. A meeting rhythm that produces decisions, a follow-up system that closes them, and the systems documentation that does not exist yet.
• Then shift from executing to anticipating. That transition is the entire difference between good support and senior partnership.

• Zero-defect logistics. Nothing dropped. Reliability first, before anything clever.
• Closure over activity. Every commitment tracked to done, including yours.
• Anticipation over instruction. Executing instructions well is table stakes; removing the need for them is the job.
• Discretion without exception. A decade of confidential exposure with a clean record.
• Structure where there was none. 60+ SOPs built across a multi-entity organization, plus a decade of process design behind them.
• Calm under pressure. Fast-moving, ambiguous, high-stakes environments are the ones I am best in.

• Founder-led and high-growth organizations where the org chart is still forming and the work outpaces the headcount
• Multi-entity or multi-venture operations requiring one person to hold context across all of them
• Leaders ready to actually delegate the calendar and the inbox — that is where most of the value lives
• Teams that need systems built, not just maintained, and want documentation and automation to come with it
• Remote and distributed environments across professional services, technology, consulting, and e-commerce
• Engagements structured as full-time, part-time, or contract, depending on what the role genuinely requires