monefy

The first three months on LinkedIn

Twenty-six posts, two a week, Tuesdays and Thursdays. Every post is written, assigned a visual direction and tagged to the blog piece it comes from. Click any card to see it full size.

26posts
13weeks
6blog anchors
14visual directions used
The 15 visual directions →

August — Reset the positioning

Nobody currently knows what Monefy is. Before anything clever, establish that we own the clinics and built the machine.
Blog anchors
A. Inside the Machine Room
B. The One-Button Billing Robot
W1Aug
Tue 11 Aug01 Documentary
ON CARDWe operate US mental health clinics. Ours — not a client's.
CAPTION · launch post · links blog AMonefy is a team in Brașov that runs five mental health clinics in the United States. Not as a vendor. We operate them, we built the software they run on, and we carry the outcome when something breaks. For two years we have been building an operating system for that work and saying nothing about it publicly. We are going to start. Real artifacts, real incidents, the ones that did not work included. First piece is on the blog.
Thu 13 Aug14 Assumption
ON CARDWhat people assume / What is actually true
CAPTION · brand haloRead our website a year ago and you would have filed us under outsourcing. Reasonable mistake — that is what most companies our size in this region do. It is also wrong in the way that matters. An outsourcer optimises for the client's brief. We do not have a brief. The clinics are ours, so when a process is bad we do not escalate it, we fix it. That single difference changes what is worth building properly.
W2Aug
Tue 18 Aug11 Map
ON CARDThe clinics are in New Jersey. The people running them are not.
CAPTION · brand haloEvery clinical appointment happens in New Jersey. Almost every system behind it is built and run from Brașov — the billing, the CRM, the call floor, the reporting. People assume that distance is the hard part. It is not. The hard part is that being far away removes every excuse for not understanding the market properly, so you end up learning it more thoroughly than someone who grew up in it.
Thu 20 Aug15 Ledger
ON CARD5 clinics · 1 clinical platform · 0 built to someone else's brief
CAPTION · recruiting + haloThe short version, for anyone who has been asked what we actually do. Five clinics we operate in the US and more opening. One clinical platform built in-house and already in daily use by our own therapists, which is a very different thing from a product built on a pitch deck. And none of it built to someone else's specification. That last number is the one that determines what working here feels like.
W3Aug
Tue 25 Aug03 Mechanism
ON CARDEvery robot we ship starts deliberately boring.
CAPTION · links blog BEveryone wants the robot that does everything. Ours starts as a scheduled job pressing one button the billing software already trusts, on a batch small enough to check by hand. It stays there for a month. If that month is clean it gets the next permission, and not before. Slower on paper. Considerably faster in practice, because we have never had to unwind one.
Thu 27 Aug10 Green flood
ON CARDHalf the value. A hundredth of the risk.
CAPTION · brand haloThe rule behind the last post, stated plainly. A first version that captures half the value at a hundredth of the risk beats a complete one that nobody dares turn on. We apply the same standard to automation that we apply to a new colleague: you get more responsibility by being right repeatedly, not by describing how right you would be.
W4Sep
Tue 1 Sep02 Split feature
ON CARD“Anything the map doesn't recognise goes to a person.”
CAPTION · links blog BThe most important line in any automation we have written is the one that says stop. Systems that try to handle every case quietly guess at the edges, and in billing a quiet guess is the expensive kind. Ours are built to fail loudly and hand the odd case to somebody who can think about it. That is not a limitation we are working around. It is the design.
Thu 3 Sep13 Open role
ON CARDSenior Python developer · Engineering · Brașov
CAPTION · recruitingWe are hiring a senior Python developer. You would be building the machinery a real operation depends on every shift — the posting robots, the reconciliation pipelines, the internal tools our billing and support teams live in. The feedback loop is unusually short and unusually honest, because the people using what you build are down the hall and will tell you directly. Details on the careers page.

September — Prove the machine

Positioning is claimed; now demonstrate it. This month is where the engineering audience decides whether we are serious.
Blog anchors
C. The Remittance Compression
D. You Literally Can't Break Anything
W5Sep
Tue 8 Sep04 Compression
ON CARD9,734 remittance lines → 177 patterns → 11 workflows
CAPTION · links blog CInsurance remittances look like chaos. Thousands of lines a month, hundreds of reason codes, no obvious order. We sorted one month of them properly and the chaos compressed: 177 recurring patterns, and 11 workflows that cover all of it. The map lives in a file our billing team maintains rather than in anyone's head, and anything it does not recognise goes straight to a person. Full write-up on the blog.
Thu 10 Sep05 Setup & payoff
ON CARDThe chaos was never chaos. It was 11 things wearing 9,734 costumes.
CAPTION · brand haloThe useful lesson from sorting a month of remittances was not the automation. It was that the volume had been hiding how small the actual problem was. Most operational messes are like this — they feel enormous because nobody has counted them. Counting is unglamorous and it is almost always the highest-leverage hour of the week.
W6Sep
Tue 15 Sep06 Carousel
ON CARDSeven rules we use to automate work nobody wants to do. 01/07
CAPTION · carousel, 7 slides · haloTwo years of building automation for our own operation, compressed into seven rules we actually follow. They are not clever. Rule 4 is the one people argue with, and it is the one that has saved us the most: if a person cannot check the output by hand at least once, it is not ready to run unattended. Swipe through.
Thu 17 Sep09 Exhibit
ON CARDMost of what we run started as an argument in front of this board.
CAPTION · cultureThis whiteboard is still in the office. Half of what is written on it was argued over for an afternoon and then quietly became how we actually operate; the other half did not survive contact with a real week. We have never found a substitute for the room where people disagree out loud before anything gets built.
W7Sep
Tue 22 Sep05 Setup & payoff
ON CARDYou literally can't break anything.
CAPTION · links blog D · recruitingWhat we tell every billing specialist on the day they first open a terminal. It is not encouragement, it is a design constraint we had to build for: every wrong move is reversible, so the only way to learn is to actually try things. Teaching non-technical staff to work in the tools directly took real engineering effort. It has repaid it more than any training programme we have run.
Thu 24 Sep13 Open role
ON CARDCRM & automation specialist · Brașov
CAPTION · recruitingWe are hiring a CRM and automation specialist. This is not a role where you maintain someone else's workflows. Our CRM is the spine of a live operation — every lead, every appointment, every follow-up runs through it — and the person in this seat decides how it behaves. If you have ever inherited a CRM someone else broke and wished you could rebuild it properly, this is that.
W8Sep
Tue 29 Sep02 Split feature
ON CARD“The people using what you built are down the hall.”
CAPTION · recruitingThe shortest description of what makes engineering here different. There is no product manager relaying a translated version of the problem. The person whose afternoon your script just ruined will come and find you, and they will be right. It is a harder feedback loop than most engineers are used to and it is the reason the tools here are unusually well fitted to the work.
Thu 1 Oct08 Triptych
ON CARDFive US clinics run their billing, CRM and call center on software we built ourselves.
CAPTION · halo + recruitingThree rooms that make up most of what we do. The call floor, where the US phone lines land. Billing, where the automations earn their permissions one month at a time. And the whiteboard, which is still how most of it starts. None of these are impressive photographs. They are just accurate ones, which felt like the right way to begin.

October & November — Convert to hiring

Two months of proof have accumulated. This month points it all at the eight open roles and lets people self-select.
Blog anchors
E. The Bookshelf Is an API
F. The AI-Allowed Interview
W9Oct
Tue 6 Oct12 Not for everyone
ON CARDWe are not for everyone.
CAPTION · recruitingAn honest warning before the hiring push. If you want a groomed ticket queue, clean documentation and a manager between you and the decisions, this will frustrate you. Most people here started with one responsibility and now own several, which is either the best or the worst thing about the job depending entirely on who you are. Worth knowing which before you apply.
Thu 8 Oct03 Mechanism
ON CARDOur interview, in three stages
CAPTION · links blog F · recruitingYou are allowed to use AI in our technical interview. Encouraged, actually — it is what you would do on the job. What we are watching for is whether you notice when it is confidently wrong. Candidates who catch it and say so score higher than candidates who write flawless code without ever looking up. The whole process is three stages and we tell you all of them up front.
W10Oct
Tue 13 Oct02 Split feature
ON CARD“How are you?” is a greeting, not a question.
CAPTION · culture · America handled softlyWe answer American phone lines every day, and the small differences are the ones that take longest to learn. Not the accent or the vocabulary — those go quickly. The register. How much warmth a stranger expects, and how quickly you are supposed to get to the point after it. Getting that wrong does not read as foreign, it reads as cold, which matters a great deal when the person calling is not having a good week.
Thu 15 Oct13 Open role
ON CARDBilling specialist · Brașov
CAPTION · recruitingWe are hiring a billing specialist. US healthcare billing is a genuinely difficult specialisation and almost nobody sets out to learn it, which is exactly why three years of it is rare and travels well. You would learn insurance eligibility, remittance logic and the clinical software from people who built the tools around it. No prior US healthcare experience required. Curiosity about how systems actually work is the real requirement.
W11Oct
Tue 20 Oct06 Carousel
ON CARDWhat your first month here actually looks like. 01/06
CAPTION · carousel, 6 slides · recruitingSix slides, no brochure language. Week one you open a terminal and are told you cannot break anything, which is true and took engineering effort to make true. By week four you own something small end to end. We wrote this down because every candidate asks the same question in the final interview and we would rather answer it before they apply.
Thu 22 Oct10 Green flood
ON CARDAn advisor that has to argue with itself.
CAPTION · links blog E · haloWe distilled the books we kept recommending to each other into something we can actually query, with one rule: it is required to give us the counter-argument before it gives us the recommendation. An advisor that only agrees with you is just a mirror with extra steps. This has killed more of our own ideas than any meeting has.
W12Oct
Tue 27 Oct09 Exhibit
ON CARDThe shelf everything else was argued out of.
CAPTION · links blog E · cultureThe physical version of the last post. Nothing on this shelf is unusual — it is the same nineteen books half of LinkedIn recommends. What is unusual is that we did the boring work of turning them into something the team consults during actual decisions rather than something we all agree was excellent and never open again.
Thu 29 Oct04 Compression
ON CARDThree months of writing, in one picture
CAPTION · quarter recap · haloA quarter of publishing, counted honestly. Everything we have written since August came out of work that already existed — we have not invented a single story for this feed. That was the whole premise and it is the part we would keep if we could only keep one. If you want the long versions, they are all on the blog.
W13Nov
Tue 3 Nov03 Mechanism
ON CARDHow a piece gets published here
CAPTION · meta · haloSince a few people have asked how this feed is made: every post starts from something that actually happened, gets checked against a list of what we will not publish, and then a human reads it before it goes out. Nothing is written to a content calendar first and back-filled with a story afterwards. That constraint is why there are two posts a week and not ten.
Thu 5 Nov01 Documentary
ON CARDStill hiring. Still not for everyone.
CAPTION · quarter close · recruitingThree months ago almost nothing about this company was public. Since then we have published how we automate, how we teach people to use the tools, how we interview and what we will not do. The roles are still open and the warning still stands. If any of it sounded like the place you have been looking for, the careers page is the next step.
×