Why automation is a focus sector
Operations still break on handoffs: email, spreadsheets, ERPs, and tribal knowledge that do not compound. We back teams that turn those seams into durable software businesses with measurable time saved, fewer exceptions, auditability where it matters, and commercial models that scale with usage or outcomes rather than headcount alone. We engage early, when product craft and operator support still change the trajectory.
We are not a late-stage industrial fund that waits for multi-million ARR before engaging. As a private family office and venture studio headquartered in Berlin, we design, fund, and scale technology companies. Automation is one of four focus sectors alongside health tech, AI, and e-commerce. Many of the strongest automation products we see sit at the intersection of those sectors (AI-assisted workflow execution, commerce ops layers, or health-adjacent admin automation). For the family-office posture, see family office at Halfmeyer. For the broader who-we-back profile across all sectors, see our Berlin pre-seed investor guide. Sister theses: AI, e-commerce (including software-led commerce), and health tech.
What we mean by automation
In our practice, automation means software-led products where the core value is reliable execution: capturing work, deciding or routing next steps, and completing outcomes across systems with humans in the loop where needed. Strong fits include workflow orchestration and process engines, ops platforms that replace brittle manual cycles, integration layers with a clear buyer and wedge, vertical automation for a painful domain workflow, and B2B tools that make exception handling, compliance trails, or multi-system coordination repeatable. For the software surface versus hardware or robotics bar, see software-led automation. For AI-delivered services and acquire-and-automate plans, see services-as-software and AI roll-ups. For the approval clock inside customers with employee representation, see works councils at your buyer. For RPA, iPaaS, and no-code automation as a product form, see RPA, iPaaS, and no-code. For manufacturing and industrial software as a factory label, see manufacturing.
Adjacent verticals such as logistics, cybersecurity, HR tech, legal tech, regtech, developer tools, proptech, or fintech ops can fit when software, data, or automation is the core and the path to a paying customer is explicit. We typically pass on capital-intensive hardware-only or robotics bets without a software surface, token-first or speculative crypto and Web3 models, pure services or body-shop consulting wrapped as product, and generic chatbot wrappers with no durable workflow ownership. If your company sits next to automation, explain the software surface, which workflow you own end to end, what makes the wedge defensible, and traction in the deck. Full adjacent-vertical bar: adjacent verticals and #clear-passes. Buyer type (B2B or B2C) is not a hard filter: #b2b-b2c.
Software-led automation (not hardware-only or robotics-first)
Halfmeyer Ventures backs software-led automation at pre-seed and seed from Berlin. When you pitch us for a typical €25,000–€200,000 check, the product surface should be software, data, or workflow execution that makes ops compound: capturing work, routing decisions, and completing outcomes across systems. Capital-intensive hardware-only or robotics bets without that software surface are usually a pass for investment. Cold pitches are welcome; we respond within 48 hours.
As of 2026, founder-facing Europe robotics and industrial-automation investor lists commonly start specialty initial checks around €500k and frame factory-floor or deep-tech hardware paths. That framing leaves vague whether a Berlin family office and venture studio will still read an early software workflow-automation deck at a smaller studio ticket. Our bar is the software product that owns a buyer workflow, not co-building robots or capex-heavy hardware without a durable software wedge. Hardware can appear in the stack when the investable surface is software; it does not replace that surface. We do not publish robotics-hardware ban lists or factory-floor SLAs. This is operator posture for our check, not engineering advice.
Use this framing when you claim automation fit:
- Strong fits: workflow orchestration and process engines, ops platforms that replace brittle manual cycles, integration layers with a clear buyer and wedge, vertical automation for a painful domain workflow, and B2B tools that make exception handling, compliance trails, or multi-system coordination repeatable.
- Usually a pass for investment: capital-intensive hardware-only or robotics without a software surface, token-first crypto or Web3, pure services or body-shop consulting wrapped as product, and generic chatbot wrappers with no durable workflow ownership. See clear passes.
- Buyer type: we back both B2B and B2C when the software bar clears. See B2B and B2C.
Disclose in the deck the buyer and workflow you replace or compress, what the software actually does, how you handle exceptions and integrations, and traction at your stage (what we look for; traction by stage). Public automation-relevant portfolio names include Sunset and ClearStack. If you want a Berlin family office and venture studio that writes €25k–€200k into software-led automation without requiring a robotics or industrial-hardware thesis, submit your deck. Keep the link view-only; we respond within 48 hours.
Services-as-software and AI roll-ups
Halfmeyer Ventures backs software-led automation at pre-seed and seed from Berlin with a typical €25,000–€200,000 check, and that check funds product, not acquisitions. If you are building software that does work people used to do by hand, you are inside this thesis and we read the deck the same way we read any automation deck. If your plan is to buy service firms and rebuild them with AI, the acquisition capital that plan needs sits far above our band, although the software layer you build underneath it can still be a company we back. Cold submissions are welcome at halfmeyer.tech/pitch; we respond within 48 hours.
As of 2026 both versions of the idea are being funded, and neither market frame is written for a founder raising a first check. On the acquisition side, one widely reported United States allocation of about 1.5 billion dollars has been earmarked since late 2023 for AI-enabled roll-ups of fragmented services firms, with the stated aim of moving margins from the range typical of labour-heavy services toward software-like levels, and the model reached Europe during 2026: a Hamburg vehicle raised more than 50 million euros in June 2026 to acquire owner-managed German service companies in the 0.5 to 5 million euro EBITDA range, and a Berlin firm came out of stealth targeting 80 million euros for a debut roll-up fund. That is holding-company capital, and the DACH succession data underneath it describes a different market from ours: a Q2 2026 survey of 119 searchers and investors found 63% of buyers targeting companies below 1 million euros EBITDA, 70% self-funded, and 59% naming access to bank and acquisition financing as their single biggest need. On the product side, the 2026 benchmark literature re-based gross margin by archetype (pure subscription software around 75% to 85%, AI-inference products around 50% to 65%, services-heavy or managed AI around 35% to 55%), insisted that inference spend and human-in-the-loop labour belong in cost of goods sold rather than operating expenses, and published automation-rate and human-intervention ladders by round. All of those numbers describe a company already running the work in production at scale.
Our read at pre-seed is narrower: we underwrite the software, and we want an honest account of how much of the work it does today. Make these easy to extract:
- What the software already does: which steps run without a person, which still have a person in them, and which are a plan. A demo-grade completion rate presented as production is the fastest way to lose a room, and saying "we do this manually today, here is the step we automate next" is not a weakness at this stage.
- Where the cost actually sits: if people deliver part of the outcome, put that labour next to model and infrastructure spend rather than in operating expenses. A software-looking margin that only works because the delivery team was booked elsewhere is a number we will unpick on the call.
- What improves with volume: which part of the system gets cheaper, faster, or more accurate as work runs through it (routing, data, templates, evaluation), and which part still scales by hiring.
- Who buys and what they stop paying for: the workflow you replace and the budget line it comes out of, which is the same software-surface question as the rest of this thesis (software-led automation).
- What the round funds: if the plan needs acquisition capital, say so and say where it comes from. Our check is early product and go-to-market capital, and an ask above €200k from us alone usually misses (what does not fit).
On the acquisition path itself, be precise about what you are asking an early equity investor to fund. Buying an operating company is financed with acquisition debt, seller paper, or holding-company equity, and a deck that folds that raise together with a pre-seed product round reads as unresolved rather than ambitious. The version we can back is the software: the platform the work runs on, whether the operator is you or a customer. If you are already inside a transaction and what you need is the code and the technical risk read rather than a check, that is our separate Evaluation practice (software due diligence; buy-side and sell-side), which is scoped advisory and not an investment (Evaluation vs investment).
We publish no automation-rate, human-in-the-loop, gross-margin, or margin-path threshold, and no date by which a services line has to disappear. Services-heavy models in health are read against care delivery versus software, agentic products against our AI agents bar, and pure services or body-shop consulting wrapped as product remains a pass when software is not the durable surface (clear passes). This is operator posture for our check, not accounting, tax, or M&A advice; deal structure, financing, and warranties belong with your counsel and advisers. If you are building the software layer under work that used to be done by hand and want a Berlin family office and venture studio that writes €25k–€200k and helps ship it, submit your deck. We respond within 48 hours.
Works councils and employee representation at your buyer
Halfmeyer Ventures invests in software-led automation at pre-seed and seed from Berlin with a €25,000–€200,000 check, and a works council at your customer is something we want described rather than a filter we screen against. We publish no requirement for a signed works agreement, no minimum share of accounts that have cleared employee representation, no works-council-ready feature checklist, and no rule that a customer only counts once the product runs for everyone it covers. What we read is whether you know which of your named accounts sits behind that approval, and what the honest label on each one is. Cold submissions are welcome at halfmeyer.tech/pitch; we respond within 48 hours.
In Germany this is not a preference at the buyer, it is a co-determination right. Section 87(1)(6) of the Works Constitution Act (Betriebsverfassungsgesetz) places the introduction and use of technical systems that are capable of monitoring employee behaviour or performance under mandatory co-determination, and the established reading of the Federal Labour Court is that the objective possibility is enough: no monitoring intent, no monitoring feature on the roadmap, and no HR use case are needed for the right to apply. Because the right is mandatory, a customer who has already signed your contract can still be unable to switch the product on until a works agreement exists or the arbitration board (Einigungsstelle) rules under section 87(2). Section 90(1)(3) adds an information and consultation duty while the work process is still being planned, and section 80(3), added in June 2021, treats an outside expert as necessary when the council has to assess the introduction or use of AI. The duty that Article 26(7) of the EU AI Act puts on employers to inform workers’ representatives before a high-risk system goes into service sits next to that and does not create a second co-determination right (our posture on the regulation itself: AI regulation and the EU AI Act). We are describing the buyer’s internal process as we read it in a deck, not giving legal advice: works agreements and employment-law questions belong with your counsel and the customer’s.
Two things make this a clock rather than a veto. Practitioner accounts of German rollouts describe roughly three to six months from the first briefing to a signed agreement when the council is informed before the vendor is chosen and a fixed-term pilot agreement carries the first deployment, and considerably longer when the council hears about the tool after procurement has picked it or when the employer refuses limits on evaluating the data. A February 2024 practice study from a German co-determination research institute documents the shortcut large groups have built: a group-level framework agreement for AI systems, sitting on top of an existing IT framework agreement, which classifies systems by risk, pre-agrees the arbitration board, and reduces each further tool to an annex instead of a fresh negotiation. Where that framework already exists, your deal can clear in weeks. Where it does not, the first system through the door pays for the whole process. Material new functions with monitoring potential can reopen a signed agreement, so a roadmap release can restart the clock at every covered account.
The constraint also tracks the size of the account rather than the sector. IAB Establishment Panel figures for 2025, published in April 2026, put about 43% of West German and 39% of East German employees in an establishment with a works or staff council, while only about 6% of all establishments have one at all, rising to about 9% of establishments with at least five employees and about 74% of those with 201 or more. The mid-market operator you sell to first usually has no council. The enterprise logo you want on the traction slide usually does. Two dates in 2026 matter as well: the regular works council elections ran from 1 March to 31 May under section 13(1) of the same act, so a number of the bodies your pipeline depends on were newly constituted this spring, and on 2 July 2026 the federal coalition announced an intention to make the introduction of software, updates, and technical systems faster while expressly preserving existing co-determination rights, with the social partners asked to put proposals forward by the middle of October 2026. The statute itself has not changed, and a plan that prices in the friction disappearing is a plan we will ask about. The discussion also runs ahead of the practice: a February 2026 union federation special issue on AI reported that only about a third of roughly 10,000 surveyed employees said their company had any AI agreement at all (the source does not state the survey period or the population).
None of this moves our bar. It changes what a signature means, which is why we read the labels on your customer list closely:
- Which stage each account is at: contract signed, running under a fixed-term pilot agreement with one team, or in production for everyone it covers. Those are three different facts about the same logo, and using the strongest of the three words for all of them is what costs credibility on the call.
- Who still has to say yes: whether the works council (or the staff council at a public buyer: public sector and govtech) has been informed, is negotiating, or has signed, and who inside the customer owns finishing it.
- What the product does with per-person data: whether purpose limits, access roles, retention periods, and a ban on using logs as individual performance data are settings in the product or a sentence on a slide. The team that already built them is the team whose next German enterprise deal clears faster, and the disclosure posture is the same one we apply to security and compliance.
- What a release does to an approval: which roadmap items add monitoring-capable functions, and whether your rollout plan assumes each covered account reopens its agreement.
- Where a slow deal actually sits: name the open gate (IT integration, data protection, procurement, works council) instead of a stage label like “in legal”, which is the same discipline we ask for in hospital and payer procurement.
What is genuinely a pass has nothing to do with the council. It is a founding side that names a large German customer and cannot say whether the system is running, or a plan that treats a mandatory approval as an implementation detail somebody at the customer will absorb. Employee representation is a buyer-side process with its own calendar, like a procurement committee or a security review, and it is the customer’s obligation rather than yours. We publish no share-of-accounts target, no approval timeline, and no required product settings, and a pending works agreement is not a weak pipeline. The bar stays the software surface (software-led automation) and an honest account of what runs today. An RPA, iPaaS, or no-code-automation label is a different product-form read (RPA, iPaaS, and no-code). Our own clock is the short one: a first response within 48 hours, then typically one to two weeks of lean diligence after a productive founder call, for a €25,000–€200,000 check from Berlin. Submit your deck.
RPA, iPaaS, and no-code automation (a label is not a filter)
Halfmeyer Ventures writes €25,000–€200,000 into software-led automation at pre-seed and seed from Berlin. An RPA, iPaaS, or no-code-automation label, or a product that sits on Zapier, Make, n8n, or UiPath, is a disclosure question, not a filter. We publish no bot-count floor, no rule that you must already replace an incumbent RPA suite, and no requirement that the product be “agentic-native” before a first read. Cold submissions are welcome at halfmeyer.tech/pitch; we respond within 48 hours.
As of September 2026, two founder-facing stories sit next to each other and neither names a Berlin family office and venture studio that reads the deck at €25k–€200k. Analyst coverage of enterprise automation has renamed the category: Gartner’s 2026 Magic Quadrant for Business Orchestration and Automation Technologies (BOAT, published September 2026) evaluates 20 vendor platforms that coordinate AI agents, robots, systems, and people, and frames the shift as graduating from task-level RPA to full business orchestration. In the same window a Berlin process-execution company closed a €5.7 million round labelled pre-seed (June 2026). Founder-facing no-code and iPaaS primers treat a Zapier, Make, or n8n wrapper as a feature of somebody else’s product. Europe specialist automation tickets commonly start well above our band. A pre-seed company with a live bot, a handful of recipes, and no “agentic” rebrand fails those gates by construction.
The market treats classic RPA as a category you leave before institutional capital, and a connector stack as unfinished work you complete first. We read the workflow. The label is not a gate. A native-feature wrapper is still a pass. This is a different question from hardware or robotics without a software surface (software-led automation), from buying service firms and rebuilding them with AI (services-as-software), from a works council at the buyer (works councils), from a freight, warehouse, or supply-chain label (logistics), and from a recruiting or people-ops label (HR tech). It is also different from using a no-code tool to build your own product (how the product was built), from a commerce listing that lives in somebody else’s store (platform apps), and from a thin prompt over a frontier API (thin wrappers). Make these easy to extract:
- What the product actually is: RPA bots, iPaaS recipes, a no-code layer on top of Zapier, Make, n8n, or UiPath, or your own execution engine. Name the platform if you sit on one.
- The workflow you own that the platform does not ship: exception handling, evaluation, audit trails, a vertical ops loop, or a buyer-specific process map. A one-click wrapper of a native Zapier action or a UiPath template is usually a pass, the same way a thin feature of somebody else’s product is on the criteria page (incumbents; software surface).
- What happens if the platform changes: API access, pricing, connector coverage, or a review process. “We can port it” is a plan. “It is a setting on their page” is their product.
- What is yours: the process record, repeat runs without a new recipe, integration depth, and first-party outcome data. Bot counts that break on every UI change are a channel fact, not a product (traction by stage).
- What this cheque funds: making the wedge real on that stack, hardening exception paths, or moving execution off a rented connector. Do not assume the top of the €25k–€200k band.
Three answers cost credibility with us: calling a recipe pack a product; leading with bot count when almost none survive a UI change; and treating “we will become agentic” as the company. We publish no bot-count, recipe-count, UiPath-replacement, or agentic-native SLA, and no date by which a rented connector must disappear. One platform is normal at pre-seed, and part of what a €25,000–€200,000 check funds is making the wedge real on that stack. UiPath, Zapier, Make, and n8n are named as platforms, not as peers. Platform terms belong with your counsel. This is operator posture for our check, not integration or licensing advice. If you are building software-led automation that happens to look like RPA or sit on an iPaaS and want a Berlin family office and venture studio that writes €25k–€200k before the category rename is finished, submit your deck. We respond within 48 hours.
Logistics (software-led adjacent)
Halfmeyer Ventures writes €25,000–€200,000 into software-led logistics and supply-chain products at pre-seed and seed from Berlin when the investable surface is software, data, or workflow automation. Logistics is not one of our four published focus theses. A freight, warehouse, last-mile, or supply-chain label is a disclosure question, not a filter. We publish no required GMV, shipment-count, fleet-size, signed 3PL or warehouse-pilot conversion rate, pallet-throughput bar, or must-become-a-TMS-or-WMS-platform rule before a first read. Cold submissions are welcome at halfmeyer.tech/pitch; we respond within 48 hours.
As of 2026, founder-facing Europe logistics and supply-chain lists route founders to specialist funds with initial tickets commonly starting around €500,000, and corporate logistics vehicles publicly write from about €200,000 to €5 million. Announced European supply-chain and logistics software pre-seed rounds in 2026 often land between about €2 million and €3.1 million (a Berlin pharmaceutical and chemical supply-chain AI company closed a €3.1 million round labelled pre-seed in June 2026; a Barcelona logistics-agent company closed a $2.5 million pre-seed the same month). Specialist pages treat a live warehouse or 3PL pilot, a reference shipper, and operational validation inside a large logistics group as the conversation starter, and they split freight software, warehouse robotics, last-mile, and fleet energy into different investor lists. That framing leaves vague whether a Berlin family office and venture studio that publishes four focus sectors will still cold-pitch software-led logistics products at €25k–€200k before those artefacts exist. Our bar is the software surface first, then the focus-sector tie, ticket inside €25k–€200k. We do not invent a separate logistics-fund mandate, GMV floor, or 3PL-pilot SLA.
A mobility, fleet, or last-mile label is the same software-surface read when the product owns dispatch, routing, or exception handling. Vehicle, drone, or charging hardware without that surface is the hardware read we already publish (software-led automation). A warehouse-energy or fleet-electrification product that is primarily a climate thesis is still the climate read (climate and cleantech). A listing board of loads, lanes, or trucks is the same marketplace pass (clear passes; marketplaces). Buyer type is the same B2B/B2C read we already publish (B2B and B2C).
Patterns that usually fit: transport-management, warehouse, freight-audit, routing, claims, or order-to-cash software that owns a buyer or operator workflow; AI-assisted logistics tools when the wedge is workflow or data rather than a prompt over a TMS or visibility API (thin wrappers vs vertical AI); last-mile or warehouse software with a productized layer; shipper, 3PL, carrier, or retailer operator tools that clear the same software bar. Patterns that usually pass for investment: load boards or listing directories of trucks and lanes without matching, pricing, trust, or workflow depth (clear passes); day-rate freight brokerage or dispatch staffing dressed as a platform; hardware-only vehicles, drones, robots, or charging kits without a productized software surface (software surface); token-first freight tokens. Hardware can sit in the stack when the investable surface remains software.
Four things make a logistics deck legible to us:
- What the software does: the workflow you own (planning, warehouse, freight audit, routing, claims, or last-mile exception handling), not a category slogan or a GMV headline.
- Which focus sector you tie to: automation, AI, e-commerce, or health tech, in one sentence.
- Who already asked, and what they asked for: a named shipper, 3PL, carrier, warehouse operator, retailer, or nobody yet. “No signed 3PL yet” is acceptable at pre-seed. “We move 2 million shipments” with no payer and no shipped product is not.
- What this round funds: product and the next proof, not a bid desk or a fleet a later round pays for.
Three answers cost credibility: calling a load board “logistics software”; leading with GMV or fleet size when almost nobody pays and nothing ships; and treating a signed 3PL logo as the company. In the deck, name logistics as the adjacent label, state the focus-sector tie, say what the software does, and disclose who pays and any known warehouse, carrier, or procurement path in plain language (we are not your counsel). Focus versus adjacent: focus sectors. Product-form RPA sits next door (RPA, iPaaS, and no-code). HR tech sits next door (HR tech). If you want a Berlin studio that cold-pitches software-led logistics inside €25k–€200k, submit your deck. We respond within 48 hours.
HR tech (software-led adjacent)
Halfmeyer Ventures writes €25,000–€200,000 into software-led HR tech, people-ops, recruiting, and workforce-workflow products at pre-seed and seed from Berlin when the investable surface is software, data, or workflow automation. HR tech is not one of our four published focus theses. A recruiting, people-ops, payroll, talent, or future-of-work label is a disclosure question, not a filter. We publish no required CHRO or Head-of-TA logo, employee-count or seat-count floor, ATS-replacement bar, HR-industry-founder rule, or must-become-a-Future-of-Work-only-vehicle rule before a first read. Cold submissions are welcome at halfmeyer.tech/pitch; we respond within 48 hours.
As of 2026, founder-facing Europe HR-tech and future-of-work lists route founders to specialist vehicles. One August 2026 pre-seed directory of 103 firms lists a $1.6 million median first cheque. Specialist future-of-work funds commonly write $500,000 to $2.5 million. Founder-facing 2026 AI-recruiting guides treat paying HR or talent-acquisition design partners and a $2 million to $10 million seed as the conversation starter, and they treat a generic ATS as a category incumbents already own. Some Future-of-Work company builders sit near a compact ticket, but they are Future-of-Work-only and often idea-stage or Day-zero. That framing leaves vague whether a Berlin family office and venture studio that publishes four focus sectors will still cold-pitch software-led people-ops products at €25k–€200k before those artefacts exist. Our bar is the software surface first, then the focus-sector tie, ticket inside €25k–€200k. We do not invent a separate HR-tech-fund mandate, CHRO-logo floor, or ATS-replacement SLA.
A works council at the buyer is the same buyer-approval read we already publish (works councils). Buying staffing firms, RPO shops, or payroll bureaus and rebuilding them with AI is the services-as-software read (services-as-software). An agentic recruiting or people-ops product is still the AI-agents read (AI agents). Hiring and people decisions under the EU AI Act are the same disclosure read we already publish (AI regulation and the EU AI Act), not a classification memo before a first check. Employer-benefits or workplace-health products are the wellness read (wellness). Learning, L&D, or career-navigation products are the edtech read (edtech). A job board or recruiter directory without matching, pricing, trust, or workflow depth is the same marketplace pass (clear passes; marketplaces). Buyer type is the same B2B/B2C read we already publish (B2B and B2C).
Patterns that usually fit: applicant tracking, recruiting orchestration, people-ops, workforce-planning, or labour-relations software that owns a buyer or operator workflow; AI-assisted hiring or people-ops tools when the wedge is workflow or data rather than a prompt over a public job board or a resume pile (thin wrappers vs vertical AI); payroll, time, or scheduling software with a productized layer; HR, TA, works-council, or deskless-workforce operator tools that clear the same software bar. Patterns that usually pass for investment: job boards or recruiter directories without matching, pricing, trust, or workflow depth; day-rate recruiting process outsourcing or staffing dressed as a platform; hardware-only time clocks or access kits without a productized software surface (software surface); token-first workforce tokens. Hardware can sit in the stack when the investable surface remains software.
Four things make an HR-tech deck legible to us:
- What the software does: the workflow you own (sourcing, screening, onboarding, scheduling, payroll, performance, or labour-relations), not a category slogan or a headcount headline.
- Which focus sector you tie to: automation, AI, e-commerce, or health tech, in one sentence.
- Who already asked, and what they asked for: a named HR, TA, people-ops, or works-council buyer, or nobody yet. “No CHRO logo yet” is acceptable at pre-seed. “We will replace the ATS” with no payer and no shipped product is not.
- What this round funds: product and the next proof, not a recruiting desk or a services bench a later round pays for.
Three answers cost credibility: calling a job board “HR software”; leading with employee count or seats when almost nobody pays and nothing ships; and treating a CHRO logo as the company. In the deck, name HR tech as the adjacent label, state the focus-sector tie, say what the software does, and disclose who pays and any known works-council, AI-hiring, or procurement path in plain language (we are not your counsel). Focus versus adjacent: focus sectors. A freight or warehouse label sits next door (logistics). A factory or MES label sits next door (manufacturing). If you want a Berlin studio that cold-pitches software-led HR tech inside €25k–€200k, submit your deck. We respond within 48 hours.
Manufacturing and industrial software (a factory label is not a filter)
Halfmeyer Ventures writes €25,000–€200,000 into software-led manufacturing and industrial products at pre-seed and seed from Berlin when the investable surface is software, data, or workflow automation. A factory, MES, shop-floor, or industrial-ops label is a disclosure question, not a filter. Manufacturing software that owns a production workflow is an automation read, not a second thesis and not a pass because the buyer is a plant. We publish no required factory-pilot conversion rate, OEM or plant logo, machine-count or OEE bar, or must-become-an-MES-or-industrial-OS-platform rule before a first read. Cold submissions are welcome at halfmeyer.tech/pitch; we respond within 48 hours.
As of 2026, founder-facing Europe industrial-software and manufacturing-tech lists route founders to specialist vehicles. Compact industrial-OS first tickets are sometimes framed from about €50,000 to €250,000. Other pre-seed deep-tech manufacturing and robotics vehicles commonly write €250,000 to €1.5 million. Later industrial-tech funds write from about €1 million. Announced European factory-intelligence and manufacturing-software pre-seed rounds in 2026 often land between about €1.1 million and €2 million (a Munich production-line AI company closed a €2 million round labelled pre-seed in April 2026; a Vienna industrial-planning company closed a €1.1 million pre-seed in February 2026). Specialist pages treat a live factory or plant pilot, an OEM or Mittelstand production logo, and shop-floor validation inside a large manufacturer as the conversation starter, and they split MES, industrial robotics, quality, and energy into different investor lists. That framing leaves vague whether a Berlin family office and venture studio that publishes automation as a focus sector will still cold-pitch software that runs a production workflow at €25k–€200k before those artefacts exist. Our bar is the software surface first, ticket inside €25k–€200k. We do not invent a separate manufacturing-fund mandate, factory-pilot SLA, or OEM-logo floor.
Hardware or robotics without a productized software surface is the same hardware read we already publish (software-led automation). A freight, warehouse, or last-mile label is the logistics read (logistics). A product that sits on Zapier, Make, n8n, or UiPath is the RPA read (RPA, iPaaS, and no-code). Buying job shops, contract manufacturers, or systems-integration firms and rebuilding them with AI is the services-as-software read (services-as-software). A works council on the shop floor is the same buyer-approval read we already publish (works councils). Plant energy, heat, or electrification that is primarily a climate thesis is still the climate read (climate and cleantech). Software for the building rather than the line is the proptech read (proptech). A listing board of machines, capacity, or plants is the same marketplace pass (clear passes; marketplaces). A thin prompt over a public MES or ERP API is the same wrapper question as in AI (thin wrappers vs vertical AI). Buyer type is the same B2B/B2C read we already publish (B2B and B2C).
Patterns that usually fit: manufacturing-execution, quality, production-planning, maintenance, shop-floor, or industrial-data software that owns a buyer or operator workflow; AI-assisted factory tools when the wedge is workflow or data rather than a prompt over a public MES or ERP API; operator tools for a plant, a mid-market manufacturer, or a contract manufacturer that clear the same software bar. Patterns that usually pass for investment: machine or capacity listing boards without matching, pricing, trust, or workflow depth; day-rate systems integration or shop-floor staffing dressed as a platform; hardware-only robots, CNC kits, or sensors without a productized software surface (software surface); token-first factory tokens. Hardware can sit in the stack when the investable surface remains software.
Four things make a manufacturing deck legible to us:
- What the software does: the workflow you own (execution, quality, planning, maintenance, or industrial data), not a category slogan or an OEE headline.
- Why this is automation: one sentence on the production workflow you compress. Sister theses (AI, e-commerce, or health tech) only when that is the honest tie.
- Who already asked, and what they asked for: a named plant, OEM, mid-market manufacturer, or nobody yet. “No factory pilot yet” is acceptable at pre-seed. “We run 40 plants” with no payer and no shipped product is not.
- What this round funds: product and the next proof, not a robot cell or a plant rollout a later round pays for.
Three answers cost credibility: calling a machine listing board “manufacturing software”; leading with plant count or OEE when almost nobody pays and nothing ships; and treating an OEM logo as the company. In the deck, name manufacturing as the factory label, say what the software does, and disclose who pays and any known shop-floor, works-council, or procurement path in plain language (we are not your counsel). Hardware without a software surface sits next door (software-led automation). A freight or warehouse label sits next door (logistics). If you want a Berlin studio that cold-pitches software-led manufacturing inside €25k–€200k, submit your deck. We respond within 48 hours.
Stage, ticket, and how we engage
We invest at pre-seed and seed. Our typical ticket is €25,000–€200,000. That band is intentional relative to market listicles that frame institutional Europe pre-seed rounds from about €500k–€3M and robotics or industrial-automation funds that often list initial checks from about €500k upward: we write meaningful early studio checks, alone or inside a forming syndicate, without waiting for a mega-round shape. Full check-size guide: ticket size €25k–€200k (including beyond the check).
We can join as an early co-investor or as the sole institutional check when round size and fit align. Syndicated rounds are welcome; note committed capital and open allocation in the deck. Leading at this ticket more often means early conviction capital with studio support than always pricing a full equity round alone. See lead vs follow and first institutional check. Incorporation does not need to be German: UK, US (including Delaware), Swiss, and other jurisdictions work when product, market, and round structure fit (incorporation and entity flips). Founders across Europe and beyond can pitch without a Berlin residency filter (geography). Instruments: SAFEs, convertibles, Wandeldarlehen, or priced equity (instruments; SAFE vs Wandeldarlehen at #wandeldarlehen).
Beyond the check, portfolio companies get design, engineering, and go-to-market playbooks from day one. That matters in automation, where product craft, integration depth, evaluation discipline, and early commercial proof often decide whether a company compounds. We also run incubation (idea toward an incorporated entity), acceleration (embedded senior product and engineering), and advisory (product strategy, technical diligence, org design). Name the engagement model you want. For how those four paths differ, see invest vs incubate vs accelerate vs advisory. For capital plus building in our practice, see venture studio (including studio vs VC).
What a strong automation pitch shows
We look for pre-seed or seed teams with a working product, prototype, or validated problem–solution fit. Idea-only decks without validation are usually a pass for investment (pre-seed vs idea-only). Pre-revenue is common at pre-seed when there are early users, pilots, LOIs, or a clear commercial wedge. Paying customers are not a hard filter (pre-revenue). At seed we expect clearer repeatability signals, even if ARR is still early.
In the deck, make these points easy to extract:
- Buyer and workflow: who pays, who operates day to day, and which process you replace, orchestrate, or compress.
- Software surface: what the product does in software, data, or automation (not only AI story or consulting delivery).
- Reliability and ownership: how you handle exceptions, audit trails, integrations, and whether you own the outcome or only suggest next steps.
- Why you win: domain depth, switching costs, data or process maps, distribution into a stack buyers already use, or unit economics that survive seat-based noise.
- Traction at your stage: users, pilots, workflows automated, retention, LOIs, or revenue; if metrics are thin, state what you validated and what this round will prove (traction by stage).
- Round terms: amount, use of funds, instrument, timing, and any committed co-investors (use of funds).
Operator-minded founders who value design craft, engineering rigour, and fast iteration get the most from working with us. Solo founders are welcome (solo founders). First-time and repeat founders are both in scope (first-time and repeat). Criteria overview: what we look for. Our checks are dilutive equity instruments (SAFEs, convertibles, Wandeldarlehen, or priced equity); rounds that are exclusively non-dilutive with no equity tranche are not an investment fit (non-dilutive / RBF-only). Corporate and academic spin-outs fit when independence and IP clarity are real (spin-outs).
Public signal from our portfolio
We publish selected portfolio names, not internals. Automation-relevant names on that public list include Sunset and ClearStack, alongside other companies across health tech, AI, and e-commerce. Public track record we state: 20+ investments, 5.6× portfolio ROI, and 100+ products built. Use those as entity facts, not as promises about your round. Full inventory: track record.
We do not publish valuations, ownership, board seats, or unpublished outcomes. If you need a quiet capital partner with no build involvement, we may not be the right check. If you want a Berlin-rooted family office and studio that can help ship product and sharpen GTM while writing €25k–€200k into automation, you are in the right place.
How to pitch us for automation
Submit at halfmeyer.tech/pitch. Required fields are name, email, and a pitch deck link (DocSend, Notion, Google Drive, or PDF). Company name is optional. Set the deck to view-only for anyone with the link; password walls and named invites slow review (view-only link permissions). Ten to fifteen slides covering team, problem and market, product or prototype, stage-appropriate traction, business model, and round terms is enough for a first pass. No full data room is required on first submit (no data room to pitch). Full deck guide: pitch deck expectations.
Cold submissions are welcome. You do not need a warm introduction. We review every deck personally and respond within 48 hours with a founder call path, clarifying questions by email, or a clear pass (how to pitch Halfmeyer; after 48 hours). After a productive call, diligence typically runs one to two weeks. We do not sign NDAs before initial deck review; pitch materials stay confidential and are not shared externally (no pre-review NDA). State automation fit explicitly so we can route the conversation against this thesis. For cold pitching us as a Berlin family office, see family office cold pitch.