SIDECAR

HerzLeben Sidecar

We sit beside the person who owns the work in life-science and healthcare companies, and take on the specialist work you can’t hire for or outsource — from meeting materials to data analysis and app development. Managers get their time back for judgment and their real job.

  • From about two days a week
  • Renew or pause monthly
  • Documents, analysis, apps
Start with a 30-minute call
02  SITUATIONS

When to call us

We respond to day-to-day requests too — the ones that never become a formal project — and get hands-on right away. Start from the situation you are in.

01A new project has started, and no one can take on PM / PMO

We run the schedule, frame the issues and coordinate across departments. Managers stay on decisions.

02Every deck is a burden — English materials for HQ never get done

From numbers to drafts, English versions and joining the meeting. The manager reviews and sends.

03We have KOL, site and case data, but answers never come quickly

We clean the data and turn it into dashboards or plain-language queries — and keep them updated.

04No one is available to pull together evidence for reimbursement or a congress

RWD and claims analysis, health-economic models and literature reviews, through to the final document.

05A launch or a new theme, and not enough hands

Site selection, training materials, reports to HQ — we take on the work that piles up at launch.

03  HOW IT WORKS

Beside the person who owns the work

A sidecar rides beside the motorcycle. We attach to the person who owns the work, and take part of it on.

Your sideManagers and team members
  • Decide
  • Review
  • Align internally
HerzLebenOur member
  • Join meetings and frame the issues
  • Finish documents, analyses and apps
  • Write procedures and hand over

Where a manager’s time goes

Before
Carrying the workJudgment
With a sidecar
HerzLeben takes it onJudgment and the real job

Illustrative only.

What changes for managers

  1. 01
    Hand over specialist work as it is

    RWD analysis, English reports for headquarters, internal study sessions — without long explanations.

  2. 02
    Leave a way of working your people can run

    We turn how it’s done into procedures and manuals, so it keeps running when people change.

  3. 03
    Less overflow into your evenings

    We work evenings and weekends. Managers get back to judgment and review.

04  ENGAGEMENT

How we work with you

  • How much

    Around two days a week, adjusted month by month. We join your meetings as an outside member.

  • Chat and meetings

    Chat any time. Meetings are scheduled on weekdays.

  • Work

    We also work evenings and weekends, and finish urgent requests over the weekend.

An example week

FriSat–SunMonTue–WedThuYouFriJoin the meeting. Asked for a deck by MondayMonDraft arrives. The manager reviewsThuSubmitted to headquarters. On to the next topicHerzLebenSat–SunWe finish itTue–WedOne line of feedback; we revise

An example week. Teal marks the days we do the work.

05  WHAT WE TAKE ON

What we take on

We take on what is needed, as much as is needed. Development is one of these.

  • 01Project managementPM / PMO, framing the issues, coordinating across departments
  • 02DocumentsInternal reports, English materials for headquarters, joining meetings
  • 03Data analysis and evidenceRWD and claims data, health-economic models, statistical analysis plans
  • 04App developmentDashboards, asking data questions in plain language, automated reporting
  • 05Procedures and handoverProcedures and manuals, handed over to your staff
Not included
  • On-site residency
  • Responsibility for running or maintaining systems
  • Development projects that take months (quoted separately)

Built along the way

Clients and data are not named; screens are recreated with synthetic data
All WORKS →
06  COMPARISON

How we compare

ConsultancyDev vendorHire / tempHerzLeben
Hands-on scopeMostly advice and decksBuild to a fixed specTasks you assignFrom planning to documents, analysis and apps
Industry knowledgeDepends on the projectLimitedDepends on the personIndustry work, data and development
Small, day-to-day requestsNot a projectNot a purchase orderIf instructedHands-on, right away
Getting startedMonths of proposals and approvalsRequirements firstMonths to hireAfter a call and an NDA, with a small topic
ContractPer projectUntil deliveryEmployment / agencyMonthly, volume adjusted each month
07  CASES

Cases

CASE 01

Pharmaceutical companyRWD team

2 weeks

PROJECTMap a globally unified statistical-programming process into Japan’s operation — a flow and procedures from data receipt to sign-off of results, ready for a leadership review two weeks out.

What triggered it, and what was hard

  • The move to a new global process was decided, with a leadership review two weeks away
  • The team was busy with analyses. The steps lived in people’s heads and were not written down
  • It had to be explained to leadership and HQ in English

How the 2 weeks went

Days 1–2InterviewsDays 3–6DraftingDays 7–8Team reviewDays 9–10Leadership reviewYouWalk us through the current flowCheck in the regular meeting; a line to steerThe team reads it through and commentsPresent to leadershipHerzLebenDraw the current flowDraft the new flow and step-by-step proceduresApply comments; draft the English briefingJoin and support; same-day fixes
ABCDEJA / EN
End-to-end process flow (five swimlanes, JA / EN). Structure only — contents are confidential

What we handed over

  • Process flow (JA / EN)The version used in the review, down to the conditions for sending work back
  • Step list and proceduresWho does what, and where it branches — one line per step
  • English briefing for leadershipReady to use as-is in the review meeting

ResultReady for the leadership review in two weeks. The team only checked in the regular meeting and read the draft through. The flow and procedures became the department standard and still run the same way when people change.

CASE 02

Pharmaceutical companyMarketing team

1 month

PROJECTDecide whether to keep or replace an external SaaS reporting tool — by prototyping equivalent screens as an in-house app, comparing side by side, and hosting it in the cloud under the company’s rules.

What triggered it, and what was hard

  • Reporting depended entirely on an external SaaS, and a renewal decision was due
  • No one in-house could evaluate an alternative; specifying and outsourcing it would take months
  • Requests kept coming during the review — producing numbers took half of every week

How the 1 month went

Week 1Inventory and prototypeWeek 2Real dataWeek 3Side by sideWeek 4DecisionYouShow the screens in use and the source dataA line on the draft screens; check the numbersUse both in the regular meetingDecide to switch; ask for what is nextHerzLebenPrototype equivalent screens on synthetic dataConnect to your environment; host in the cloud under your rulesPrepare the comparison and the migration planLeave procedures; keep building after the switch
Dashboard screen (client and data withheld; recreated with synthetic data)

What we handed over

  • Clinical-practice dashboardRegions and sites on one screen, in a form your team can keep developing
  • Ask the data in plain languageAsk in Japanese; get tables and charts back
  • Procedures and migration planSo it keeps running when people change

ResultThe SaaS screens were replaced with an in-house app, and we keep building apps large and small as the team asks. People ask the app directly, and it is used as-is in the regular meeting.

Client names are withheld.

08  CONTRACT

How the contract works

  • A monthly subscription

    We agree next month’s volume and topics together, and you can revisit them at any time.

  • Switch it on when you need it

    Turn it on for a project launch or ahead of a headquarters review, pause when things settle, and resume later.

  • More days, or on site

    For periods that need three or more days a week, or work at your office, we agree the volume and format together.

An example year2 days / wk3+ days / wkPaused
Project launchM1
M2
M3
PausedM4
M5
Before HQ review / congressM6
M7
M8
PausedM9
Steady stateM10
M11
M12

Illustrative on/off pattern and volume.

Fees and detailed terms are explained when we talk.

09  GETTING STARTED

Getting started

  1. STEP 1Talk

    About 30 minutes online, about your work and what is in the way (free).

  2. STEP 2NDA

    Signed before we look at internal work or documents. Your template is fine.

  3. STEP 3Share the issue

    We review your work and materials and pin down the issue. Where useful, you try apps we have built.

  4. STEP 4Proposal

    We agree the topics, the approach and the volume.

  5. STEP 5Start

    We sit beside the person who owns the work, and get going.

10  FAQ

FAQ

Can we start with just one person?

Yes. A whole department, or a single manager — either works.

Can we ask for small, day-to-day things that are not a project?

Yes. Send a line in chat and we get hands-on right away. That is exactly the kind of work we are here for.

Can you handle English reports for headquarters and global meetings?

Yes. We write English materials and join global meetings.

How do you handle our internal data?

Under an NDA, following your rules and compliance. We use only the generative AI tools you have approved, and your data stays in your environment. We have declared IPA SECURITY ACTION (two stars).

Can you run training or study sessions?

Yes, as part of the work: we hand things over to your team through procedures and study sessions. We also run corporate training in AI-driven development (TRAINING), starting with a free 2-hour session.

Tell us about the work that is in the way

The first conversation is free — about 30 minutes online, about your work and what is in the way.

Get in touch