Moritz Dausinger had already sold three businesses when he discovered that experience could still lead him into a familiar ditch. He started building Refiner with a useful little idea, then spent much of 2019 developing something customers had never requested. Eventually, he scrapped most of the code. A founder with several exits had given himself the beginner’s assignment again: make something people actually want.
There is an appealing lack of ceremony about this admission. Success usually acquires a publicist somewhere along the way. Dausinger tells the awkward part himself. The founder and CEO of Refiner, based in Paris, has made a career out of practical software: tickets, email data, document processing, customer questions. His work concerns the small pieces of business that become surprisingly expensive when nobody has fixed them.
Refiner asks people questions inside software. Its founder’s own history suggests why asking sooner might have been useful.
A detour through Toulouse
France first entered his working life through an internship at Airbus in Toulouse. He was studying at the Technical University of Munich, where his education included human-machine communication and machine learning. His public education record runs from 2003 to 2009. The eventual maker of survey widgets had spent time with rather larger machines.
After university, he joined the Fraunhofer Institute in Stuttgart with a doctorate in view. He left that path and moved to France, where his then-girlfriend lived. He started his first company with her roommate in Nancy. Entrepreneurship arrived through a combination of programming ability, personal geography and an available collaborator. The origin has the agreeable untidiness of an actual life.
His technical background made the risk feel manageable: he believed he could find programming work again. That is a more useful detail than a retrospective declaration of fearlessness. He could try something uncertain because he had a skill to fall back on. The adventure came with a return ticket.
Tickets, then the inbox
The first company made ticketing software for event organisers. It was acquired by Weezevent, and Dausinger became CTO there. That placed him inside a venture-backed business, with the opportunity to see how a growing company operated from the technical side.
Later came Mailparser, which extracted structured information from recurring emails. Its business was easy to recognise if you had ever watched somebody copy the same fields into a spreadsheet all afternoon. The customer’s problem had the glamour of office plumbing. Office plumbing, however, tends to have a budget.
He sold Mailparser to SureSwift Capital in 2016 while keeping its younger sibling, Docparser. That product extracted information from documents such as PDFs. SureSwift bought Docparser in 2018. Selling the two separately mattered: it let him release one established operation while continuing to develop another. An exit could be a change in the workday, rather than the final scene of a career.
The $400 ambition
Mailparser began with modest expectations. Dausinger remembered thinking that $400 a month would be a welcome contribution to the rent. He was working elsewhere and exploring a technical idea, rather than appointing himself the leader of a large future organisation.
A Hacker News launch brought attention but initially no paying customers. Conversations with Zapier’s founders gave him encouragement and a clearer sense of demand. The useful result of showing his work was a relationship, followed by leads. A busy launch day and a functioning business turned out to be different appointments.
By the time he chose to sell Mailparser, he put its monthly recurring revenue at around $30,000. That figure describes Mailparser at that point in his story. What makes it interesting is the distance from the original ambition. A side project had become substantial enough to force a decision about the kind of job he wanted: keep expanding its operation, or return to building a younger product.
Two questions that became a company
At Docparser, different people arrived with very different intentions. Some were browsing. Others represented organisations with substantial document-processing needs. A signup form could collect an email address without explaining much about either group.
Dausinger’s improvised solution was to ask about the volume and type of documents people processed. Those answers made it easier to understand customers and decide who might benefit from a personal conversation. The question was practical: how could the business learn enough to help, while letting somebody get on with trying the software?
Refiner’s early direction drifted towards a complicated lead-qualification product. In 2019, Refiner was being described publicly as a lead scoring and qualification tool for self-service B2B software companies moving upmarket. Even the public description had travelled some distance from a small survey inside an app. The reset brought that simpler starting point back into view.
A launch is a beginning with better lighting
Refiner launched on Product Hunt in March 2020 and finished fourth for the day. Dausinger later said the launch brought no paying customers. He had wanted attention, early users and feedback; those were different measures from a subscription payment.
His detailed early account dates the first paying customer to July 2020. Reaching ten then took only a few weeks. The long period before that first payment is a useful corrective to the neatness of launch announcements. A product can be publicly available well before it has demonstrated that somebody will pay for it.
He had also begun publishing useful material before launch, expecting search traffic to take time. That patience sits alongside his taste for making things. The software could be written and released; attracting suitable customers required its own, slower work. A finished interface was never going to do every job in the company, however handsome the buttons.
“done is better than perfect”
Moritz Dausinger, on the tension between shipping and polishing
The difficult courtesy of saying no
In his follow-up account of Refiner’s growth, Dausinger described analysing what its happiest customers valued. The resulting decision was to concentrate on software companies. It also meant declining some uses from people who were already customers. Focus had a cost that could answer back.
He reported that Refiner’s monthly recurring revenue nearly quintupled during 2021. The narrower positioning informed its website, product priorities, marketing and pricing. The point was to make those choices coherent around a recognisable buyer, rather than ask one tool to satisfy every possible survey request.
There is a personal consequence to this sort of decision. A developer can almost always imagine another feature. Each accepted request creates work, documentation and expectations. Saying no gives the remaining promises a better chance of being kept. For someone drawn to building, a clear boundary can be a useful colleague.
A small team still needs colleagues
Small teams recur throughout Dausinger’s career, but small has never meant that every task must belong to him. In his 2023 conversation with Anna Nadeina, he discussed using freelancers through lasting relationships and retainers. The arrangement depended on continuity, expectations and company culture, even with only a handful of people involved.
His approach also exposed a founder’s familiar difficulty: support consumes time, yet good support is part of what makes customers stay. Documentation, the product interface and the experience of getting help all belong to the same working system. Hiring a few capable people does not remove the need to think carefully about how that system behaves.
The preference for a compact operation is therefore a management choice with daily obligations. Somebody must follow up. Somebody must explain the problem. Somebody must make the next customer’s path a little less confusing. The headcount can remain small while the list of responsibilities becomes quite grown-up.
The survey should know when to leave
Dausinger’s customer-feedback advice contains an endearing restraint for someone who sells surveys. Timing matters. Let people explore. Avoid interrupting a task. Ask the relevant people, and keep the questions short.
In discussing customer success, he recommended connecting responses to user profiles and moving that information into the tools a team already uses. A score sitting in a report offers fewer possibilities than an answer that helps somebody decide whom to contact or what to improve. The usefulness begins after the response arrives.
His own description of customer success leaves room for a human at the end of the machinery. “Try to figure out who the relevant people are, and only ask them.” It is good survey advice. It also sounds like a reasonable policy for meetings, newsletters and most of the internet.
An unexpected passenger
Dausinger’s influence travelled beyond his own products. Arvid Kahl heard him discuss selling Mailparser on the Indie Hackers podcast in 2017. Kahl was travelling through Berlin when the possibility of selling a small software company to a private-equity buyer caught his attention. He later sold his own software business to the same buyer.
When they spoke in 2023, Kahl thanked him for making that possibility visible. Dausinger, for his part, has said he initially hesitated to accept his first podcast invitation. The conversation he nearly declined had become useful to a listener he did not yet know. Software founders tend to measure distribution in visits and conversions; occasionally an idea takes a much longer route.
By then, Dausinger had also accepted investment from Calm Company Fund, choosing funding he considered compatible with his preferred way of building. He wanted room to keep contributing to products. Refiner had given him another chance to arrange that work, after reminding him how easily the work can get away from you.
His career keeps returning to a modest question with demanding consequences: what would make this useful? The answer has taken him from ticketing to email, documents and surveys. Sometimes it has required another feature. With Refiner, it once required deleting most of them.