H Company

H Company

Autonomous AI agents for enterprise workflows

Overview

H Company builds autonomous virtual humanoids that operate enterprise software and execute complex digital workflows at scale. Their AI agents are multimodal vision-language models (the Holo series, including Holotron-12B) that interact directly with user interfaces across web, desktop, ERP/CRM and internal tools without traditional API integrations. They perceive context, plan multi-step actions, and execute tasks to act as autonomous digital operators embedded in business workflows, delivering measurable productivity gains through ROI-focused Forward Deployed Engineering engagements. They collaborate with NVIDIA on Nemotron architectures and aim to become a global leader in enterprise autonomous AI for large organizations.

About H Company

Simplify's Rating
Why H Company is rated
B-
Rated B on Competitive Edge
Rated B on Growth Potential
Rated C on Differentiation

Industries

Data & Analytics

Enterprise Software

AI & Machine Learning

Company Size

201-500

Company Stage

Seed

Total Funding

$220M

Headquarters

Paris, France

Founded

2024

Get referred to H Company

See people who can refer or advise you

Simplify Jobs

Simplify's Take

What believers are saying

  • Holo3.1 launched June 1, 2026 with 0.8B-35B models and quantized formats.
  • H Company and FDJ UNITED announced a strategic partnership on November 17, 2025.
  • NeoMME shipped September 3, 2026 under Apache-2.0, expanding open-source retrieval credibility.

What critics are saying

  • Laurent Sifre stepped down as CTO in May 2026, weakening technical continuity.
  • Three cofounders left in August 2024 over operational differences, signaling persistent leadership instability.
  • MacArena exposed 26% macOS-native performance drops; brittle cross-platform agents kill enterprise trust quickly.

What makes H Company unique

  • H Company sells computer-use agents that control web, desktop, and mobile interfaces directly.
  • Holo3.1 ships quantized local checkpoints, enabling private on-device deployment without leaving customer networks.
  • FDJ UNITED works as a design partner, giving H Company live enterprise workflow access.

Help us improve and share your feedback! Did you find this helpful?

Funding

Total Funding

$220M

Above

Industry Average

Funded Over

1 Rounds

Notable Investors:
Seed funding is usually the first official round after pre-seed, when a startup has a prototype or concept. It’s typically used to develop the product, test the market, and start building the team. Investors here are often angel investors or early-stage venture capitalists.
Seed Funding Comparison
Above Average

Industry standards

$3.3M
$2M
Netflix
$2.3M
Instacart
$3M
Robinhood
$220M
H Company

Benefits

Hybrid Work Options

Professional Development Budget

Growth & Insights and Company News

Headcount

6 month growth

-5%

1 year growth

-3%

2 year growth

-1%
Sifted
Sep 4th, 2026
H cofounder Laurent Sifre joins Microsoft

Laurent Sifre, cofounder of Paris-based agentic AI startup H Company, has joined Microsoft, Sifted has learnt. The move sees Sifre transition from the French AI startup to the US tech giant. H Company focuses on agentic AI technology. No further details about Sifre's role at Microsoft or the circumstances of his departure from H Company were disclosed.

Addis Pulse Studio
Sep 4th, 2026
NeoMME matches a retriever 14x its size at 260M parameters.

NeoMME matches a retriever 14x its size at 260M parameters. H Company pretrained a multimodal encoder from scratch instead of repurposing a generative VLM, and released the weights under Apache-2.0. 4 September 20265 min read1,085 words 30-Second summary. * H Company released NeoMME, a family of 260M- and 800M-parameter multimodal multilingual encoders pretrained from scratch, on 3 September 2026 under Apache-2.0. * The 260M retrieval checkpoint scores 0.523 nDCG@10 on ViDoRe v3 - within 0.002 of ColQwen2.5, which carries roughly 14x more parameters. * Hierarchical pooling plus asymmetric quantization cuts a page's late-interaction embedding from about 1.5 MB to 6 kB while keeping over 95% of baseline retrieval quality. What happened. H Company published NeoMME on 3 September 2026: two multimodal multilingual encoders, 260M and 800M parameters, with pretrained backbones and retrieval-tuned checkpoints on the Hugging Face hub under Apache-2.0. The paper - NeoMME: A Single-Tower Multimodal-Native Multilingual Foundation Encoder for Efficient Fine-Tuning and Inference, by Aurélien Lac and Tony Wu - went to arXiv on 31 August 2026 as 2609.01657. The architecture is the argument. Retrievers like ColPali take a generative vision-language model - a separately pretrained vision tower bolted to a causal language model - and press it into service as an encoder. NeoMME is a single bidirectional Transformer with no vision tower and no decoder. Images enter as non-overlapping 32x32 patches through a small MLP; text enters through factorized embeddings over a 131k-token BPE vocabulary. Most layers run symmetric sliding-window attention, with global attention every sixth layer and at the end. Both sizes hold a 16,384-token context, which the paper puts at two standard 4K UHD images. Pretraining ran a masked discrete-diffusion text objective over roughly 524 billion packed tokens, 290 billion of them text-only, conditioned on visible image patches for the multimodal examples. The retrieval fine-tune trains a dense head and a late-interaction head jointly and returns both from one forward pass: a 1,024-dimensional pooled vector with Matryoshka cut points, alongside a 128-dimensional vector per token and per patch. Why it matters. On ViDoRe v3, NeoMME-Retriever-260M reaches 0.523 nDCG@10 - the best of any evaluated model strictly below 800M parameters, and within 0.002 of ColQwen2.5 at about 14x fewer parameters. The 800M variant reaches 0.556, within 0.009 of the similarly sized Vultron Retriever Flash. At a matched 2048x2048 input on an NVIDIA L40S, the 260M model encodes about 51 pages per second against ColModernVBERT's 26. The compression numbers matter more. A page's late-interaction embedding starts near 1.5 MB. Pooling factor 10 with int8 brings that to 39 kB and retains over 99% of baseline quality; pooling factor 8 with int8 queries and binary documents brings it to 6 kB, 255x smaller, with over 95% retained. H Company also contributed the model upstream, so NeoMMEForRetrieval is a Transformers class rather than trust-remote-code. Builder insight. The benchmark table is not the interesting result. A 0.002 nDCG@10 gap is a tie, and ties on ViDoRe get published every month. What the tie demonstrates is that the parameter cost of the ColPali recipe was overhead - a decoder that never generates, a vision tower pretrained for a different objective, causal masking on a task with no causality. Strip those and the score survives at a fourteenth of the size. That is a negative result about the standard recipe dressed as a positive one about a new model, and the negative half is the more useful finding. For a small studio the number that changes what is shippable is 6 kB per page. Late-interaction retrieval has always been gated on index size rather than index quality: at 1.5 MB per page a 100,000-page corpus is a 150 GB index, which is a served-infrastructure problem with a monthly bill. At 6 kB it is 600 MB, which fits in RAM on a machine you already own. This release moves the affordability line considerably further than it moves the quality line. What H Company is not saying deserves equal weight. No VRAM figure appears in the paper, the blog post or the model card - the L40S throughput number comes off a 48 GB datacentre card and implies nothing about a 16 GB consumer GPU. And "multilingual" is never enumerated; no language list appears in any of the three sources, so coverage outside the usual European set is unverified until you test it. The parameter counts also disagree slightly: the paper and blog say 260M, the retriever model card reports 263M. Practical implementation. The retrieval class ships in Hugging Face Transformers upstream, and the blog points at the main branch, so install from source until a tagged release carries it: pip install "git+https://github.com/huggingface/transformers" pip install "sentence-transformers>=6.0.0" # only for the ST dense/late checkpoints pip install accelerate # for device_map="auto" Loading the 260M retriever is three lines: from transformers import AutoProcessor, NeoMMEForRetrieval processor = AutoProcessor.from_pretrained("Hcompany/NeoMME-260M-Retriever") model = NeoMMEForRetrieval.from_pretrained( "Hcompany/NeoMME-260M-Retriever", device_map="auto") Six checkpoints are published: the NeoMME-260M and NeoMME-800M backbones, their two -Retriever variants, and NeoMME-260M-Retriever-ST-dense and -ST-late for Sentence Transformers. The default image ceiling is 2,048 pixels on the longest side, and the patch grid follows: 2048 / 32 gives 64 patches per side, so a square page costs 4,096 of the 16,384 context slots and leaves ample room for the query. Plan indexing throughput from that, not from page count alone. No source states a memory requirement. Before wiring this into a pipeline, run the 260M checkpoint at your real page resolution on your actual card and log peak allocated VRAM and pages per second - at this parameter count the binding constraint is far more likely to be activation memory at high resolution than weights. If you serve non-English documents, build a small labelled set in your target languages and measure recall before trusting the word "multilingual". License. Apache-2.0, stated in the paper abstract and in the license field of the model card metadata. Commercial use is permitted with no per-use fee, no non-commercial clause and no revenue or deployment ceiling; the obligations are the ordinary Apache-2.0 ones - preserve the licence and notice files, state significant changes, and accept the patent grant and its termination clause. Backbones and retrieval checkpoints carry the same terms, so a fine-tune of your own on top of the backbone takes on no additional restriction from H Company. Sources. Addis Pulse Studio build these. Addis Pulse Studio designs and runs production AI workflows - private stacks, creator tooling, and the pipelines behind them. addispulsestudio.com neomme open-weights retrieval multimodal encoders How this post was made. Drafted from clustered primary sources by the models below, then read, edited and approved by a human before it was published. The sources are listed in full at the end of the article. * Drafted - 2026-09-04 14:40 UTC * Independent sources - 3 * draft article - claude-opus-5 * short script - claude-opus-5 * Run - radar-20260904T140206Z

Clawvard
Jun 8th, 2026
Computer-Use Agents in 2026: how good they are and how to run one locally.

Computer-Use Agents in 2026: how good they are and how to run one locally. Computer-use agents - AI systems that operate a real graphical interface by looking at the screen and clicking, typing, and scrolling like a person - crossed an important line in June 2026. On June 2, H Company released Holo3.1, a computer-use model family with checkpoints small enough to run on a laptop. Days later, two new research efforts landed: MacArena, a benchmark that runs agents inside real macOS, and a paper on long-horizon web agents that pinpoints why these systems lose the thread on long tasks. Together they mark the moment computer-use agents stopped being demo-ware and became something you can actually evaluate and run yourself. This piece pulls those threads together: what computer-use agents can genuinely do today, how the latest benchmarks measure them, where they still break, and what it takes to run one locally instead of through a cloud API. What is a computer-use agent? A computer-use agent is an AI model that controls a computer through its graphical user interface rather than through a purpose-built API. It perceives the screen - via vision and control primitives, in MacArena's framing - and issues actions like clicks, keystrokes, and scrolls to accomplish a goal. The appeal is generality: instead of wiring a custom integration for every app, you point the agent at the same UI a human uses. Holo3.1 is built exactly for this, targeting GUI automation across web browsers, desktop applications, mobile (Android) environments, business and e-commerce workflows, and collaboration tools. The category overlaps with web agents, which operate inside the browser specifically, and the two share the same core challenge: reliably grounding a high-level goal into a long sequence of low-level UI actions without drifting off course. How good are computer-use agents in 2026? Good enough to be useful in specific domains, and still clearly short of reliable general competence. The honest picture comes from looking at progress and limits side by side. On the progress side, Holo3.1 posts concrete gains over its March 2026 predecessor, Holo3. On the AndroidWorld mobile benchmark, H Company reports its flagship 35B-A3B model rising from 67% to 79.3%, with the 4B and 9B variants both climbing from 58% to 72%. The company also reports a 25% improvement over Holo3 in its own Holotab product harness, and says its new native function-calling protocol reaches near-parity with the structured-JSON output it carried over from Holo3. The model family is built on the Qwen family and is explicitly engineered for robustness across what H Company calls the three production dimensions: environments, agent frameworks, and deployment targets. On the limits side, MacArena delivers the cold water. When researchers built a benchmark of 421 manually verified tasks across 50 macOS applications and ran agents against it, they found that model rankings invert between ported tasks and macOS-native ones - with a leading model trailing by over 26% on the MacArena-native subset. Their conclusion is pointed: strong scores on existing benchmarks often reflect "familiarity with task distributions rather than genuine cross-platform GUI competence." In other words, an agent that looks great on a Linux-based benchmark can fall apart on a Mac, because it learned the test, not the skill. The takeaway: treat per-domain numbers as real, but be skeptical of any claim of broad, platform-independent ability. How are computer-use agents benchmarked? The newest benchmarks share a theme: test agents in real environments, not simplified stand-ins. MacArena, accepted to the Second Workshop on Agents in the Wild at ICML 2026, runs on Apple's native Virtualization framework on Apple Silicon - real macOS, not an emulated x86 approximation. Its 421 tasks combine ported OSWorld tasks, content drawn from the earlier macOSWorld, and 49 brand-new macOS-native tasks. The design directly targets a gap the authors identify in prior work: macOSWorld covered mostly first-party apps with simpler tasks on incompatible x86 VMs. By running native and mixing in genuinely new tasks, MacArena shows that macOS "presents distinct GUI challenges beyond what Linux-based benchmarks capture." For web agents specifically, the long-horizon question is less about any single click and more about whether the agent can stay coherent across dozens of steps. A June 2026 paper, Signal-Driven Observation for Long-Horizon Web Agents, identifies the culprit: web agents ingest the raw DOM and accessibility tree - "routinely tens of thousands of tokens" - at every single action step. The authors call coupling observation frequency to action frequency "an architectural mistake," because the flood of context causes "progressive context degradation that erodes reasoning well before tasks complete." Their proposed fix, Signal-Driven Observation (SDO), is instructive even if you never implement it: a dedicated sub-call reads the full DOM but returns only the task-relevant elements and their selectors, and that sub-call is re-invoked only when a lightweight signal detector fires - on URL transitions, newly visible interactive elements, action failures, or external browser events. The principle, borrowed from Recursive Language Models, is that "querying a document outperforms reading it wholesale." The broader argument for anyone evaluating web agents: observation compression is "a core architectural decision," not an afterthought - so when you compare agents, look at how they manage context over long tasks, not just whether they can do one step. Can you run a computer-use agent locally? Yes - and that's the most practical shift in this release cycle. Holo3.1 ships in four sizes aimed at different deployment targets: Holo3.1-0.8B for ultra-lightweight local agents, Holo3.1-4B for cost-efficient deployment, Holo3.1-9B for balanced performance and latency, and Holo3.1-35B-A3B for state-of-the-art performance. Crucially, H Company publishes quantized checkpoints for local inference - including Q4 GGUF builds for running on consumer Windows and Mac hardware, plus FP8 and NVIDIA NVFP4 formats. The privacy story is the point: H Company describes a fully private deployment with "nothing leaving the user's network," and offers a pattern where an optional DGX Spark on the same local network handles model inference while the agent itself runs locally. For teams that can't send screen contents of internal apps to a third-party API, a local computer-use agent is suddenly viable. Performance under quantization is reported as surprisingly cheap. On a DGX Spark, H Company says the 35B-A3B model in NVFP4 W4A16 hits 1.41x the throughput of FP8 and 1.74x of BF16, while OSWorld scores for FP8 and NVFP4 land only about two points below BF16. End to end, they report roughly a 2x agent speedup, with average step time dropping from 6.8 seconds to 3.3 seconds. The headline: quantizing for local or on-prem use costs little accuracy and meaningfully improves speed. What should you actually take away? For Clawvard readers building on agent infrastructure, three durable lessons survive past this news cycle: * Benchmark on your real environment. MacArena's rank inversions are a warning: a model's leaderboard score may not transfer to your OS, your apps, or your task distribution. If you're going to depend on a computer-use agent, test it where it will run. * Treat context management as architecture. The long-horizon web-agent work shows that how an agent observes its environment - not just how smart the base model is - determines whether it survives a long task. Favor designs that query for relevant state instead of re-reading everything each step. * Local is now a real option. Quantized checkpoints that run on consumer hardware with small accuracy loss change the calculus for any team with privacy or cost constraints. You no longer have to choose between capable computer-use and keeping screen data in-house. Computer-use agents in 2026 are powerful in the domains they've been measured on and brittle outside them - which makes rigorous, environment-matched evaluation the difference between a useful deployment and a flaky one. Related reading. If you're evaluating or deploying computer-use agents, explore how Clawvard helps teams run and measure agents on infrastructure they control - and follow its updates as the benchmarks keep evolving.

Startup Researcher
May 16th, 2026
H Company cofounder Laurent Sifre steps down as CTO after $220M seed round

H Company co-founder Laurent Sifre has stepped down as chief technology officer to lead the startup's new scientific council, following its record $220 million seed round. Raphaël Millière, an expert in computational linguistics and philosophy, will assume the CTO role. The Paris-based agentic AI startup has undergone significant leadership changes since its founding. Three of five original co-founders departed shortly after the major funding announcement, and former Palantir director Gautier Cloix was appointed CEO in June 2025. The restructuring reflects H Company's shift from foundational research towards commercialisation and product scaling. The company develops autonomous AI systems capable of reasoning and executing complex multi-step workflows, recently releasing Holo 3 in March 2026 to enable agents to navigate user interfaces and complete enterprise tasks.

Les Echos
Apr 15th, 2026
"Mice and keyboards will soon no longer exist at all": H Company launches its consumer AI agent.

"Mice and keyboards will soon no longer exist at all": H Company launches its consumer AI agent. Model providers are rushing into agentic AI, capable of acting autonomously and automating tasks. To stand out, H is based on "computer use," meaning exactly what a human does on their machine. Published April 15, 2026 at 07:00 Reserved for our subscribers A tool capable of taking over your search engine and navigating for you? That's what the French startup H Company announced this Wednesday. Holo Tab is an autonomous agent, in the form of an extension, that each user can now add to their web browser (Google Chrome today, other browsers soon). "Today, everyone knows how to use a chatbot. Our agent, based on 'computer use,' meaning exactly what a human does on their machine, can go further in an automated way. Based on a simple prompt, the agent can perform actions it has never done before," describes Gautier Cloix, head of H since September. This content is reserved for Access and Premium subscribers Do you want to read more?

Recently Posted Jobs

Sign up to get curated job recommendations

H Company is Hiring for 5 Jobs on Simplify!

Find jobs on Simplify and start your career today

Don't see your dream role? Check out thousands of other roles on Simplify. Browse all jobs →