🧾 We Never Made It to the Trial We Promised You

Signed in April. Cancelled in June. What we actually learned had nothing to do with Rentvine.

Back in the spring we told you we were leaving AppFolio after eleven years, and that we would report back on how the replacement went.

Here is that report, and it is not the one I planned to write.

We signed the Rentvine service agreement on April 17. The onboarding fee was waived, confirmed in writing. The plan was to move one owner's portfolio over, run it alongside AppFolio for three or four months, and tell you what we found.

The data import finished June 11. We sent the termination June 24.

Thirteen days with the system. Sixty-eight from signature. We never went live, no tenant was affected, and we are still on AppFolio today.

And I want to be clear that I did raise this before we signed. Wisconsin's $25 application cap came up early, because it always does, and I was told they would work with us on it. I was also told we were not their only Wisconsin client, which I took as a good sign — somebody else had already run this road and it worked.

What I did not do was ask the next question. I never asked what working with us on it would actually look like in practice.

🔟 The number that stopped it

On the morning of June 24 I got on a call with their application and screening specialist and asked something I should have asked in April.

What exactly do you charge us per application?

Ten dollars. Screening runs $22 on top of that, built from a $10 credit pull, $7 criminal, and $5 eviction.

None of this is hidden. The $10 is published on their own site, and it covers real things — payment processing, no merchant account, no gateway, no chargeback headaches. Their model assumes the applicant pays it. In most states the applicant does, and nobody thinks about it twice.

📋 Then there is Wisconsin

Wis. Stat. 704.085 lets us charge an applicant our actual cost for a credit report, capped at $25. Actual cost. Twenty-five dollars, all in.

Their $22 fits under that cleanly. That is deliberate, and when I raised the cap on the call, they knew exactly what I meant.

But $22 plus $10 is $32. There is no version of that I hand a Wisconsin applicant. So the $10 becomes ours — every application, approved or denied, abandoned halfway, or filed three times over by a roommate group that ends up signing somewhere else.

A significant share of what we manage is student housing. First-time renters, some of them on scholarship, applying in volume when the season opens. In a market where application fees run $75 or $150, a $10 pass-through is a rounding error nobody argues about. Here it is a statutory wall.

This was the working with us I had been assured of back in April. Set the in-portal fee to $0, which means the applicant does not pay through the platform at all. So how does the money actually get to us? Somebody hands us cash at the office. Or we run a card on a separate terminal. Or we send a payment request from some other app, then match it back to an application sitting in a system that has no record of it. Then we reconcile all of that by hand and get billed for the screening afterward.

It is a legally compliant answer. It is compliant the way telling someone to walk is a compliant answer to a question about the bus. That was the dealbreaker, not the ten dollars.

📐 What the migration actually forced us to do

Here is the part that had nothing to do with Rentvine, and it is the reason I would run this exercise again.

You cannot migrate what you have not documented. To move a portfolio you have to lay out every workflow in the open: how an application moves, who touches a work order and in what order, which reports go to owners and when, what happens between a notice to vacate and a new lease. Not how it is supposed to work. How it actually works, on a Tuesday, when the person who normally does it is out.

So we mapped it. All of it. And mapping it is how you find the gaps — the step that only exists in one person's head, the report somebody builds by hand every month because nobody checked whether the software already produces it, the automation two people run differently.

That is not a discovery about our software. That is a discovery about our operation, and it is the kind of thing you only see when you are forced to write it down.

So we are doing two things at once. We are going back through the platform we already pay for, feature by feature, making sure every person on the team is using it the best way it can be used instead of the way they were shown once in 2019. And we are rebuilding the SOPs around what we found, in a format that travels — so that whenever we do move, and we will look at moving again, the operation moves with us instead of getting rebuilt from scratch.

📚 Which is why they are going on PMAdvisor

Those SOPs are not staying in our drive.

I wrote recently about what PMAdvisor is and why we built it — a place to put the operational work that never makes it into a webinar, from people who actually have to run a portfolio with it. This is exactly that. The application workflow. The work order routing. The turnover sequence. Written the way we run them, with the gaps we found already closed.

For our VA clients, this is the piece that matters most. A virtual assistant is only as good as the process you hand them. Give someone a vague instruction and you get vague work, every time, and then everybody decides the VA was the problem. Give them a documented sequence with the decision points spelled out and they run it better than the person who was doing it from memory.

That is what we are publishing. Not theory, not a template somebody sold us. The actual sequences, tested on a real portfolio, in a form your team can pick up and use.

🚪 What made leaving free

A handwritten line on the signature page giving us the right to cancel on 30 days' notice. Someone on our side asked for it before signing. It overrode the twelve-month term, and walking cost us nothing.

That one line is the reason this is a story about time instead of a story about money. The expensive stuff is almost always in the part nobody reads out loud.

Read your signature page. Then ask for that line.

🤝 Where this actually stands

Rentvine is not a bad platform, and I am not writing them off. Onboarding was responsive throughout. Historical documents did not carry over in the core migration, which we were told plainly and planned around. When active work orders did not migrate automatically, our implementation specialist moved them by hand at no charge. After we cancelled, someone senior reached out to address the $10 directly rather than letting it go.

That is not a company squeezing anybody. It is a structural mismatch with one state's law, in a corner of the market most of their customers never touch. If a Wisconsin-compatible application flow exists later, I will look at it again, and I will say so here.

As for AppFolio, I am still looking. I am always looking, and I do not think that ever stops if you are running this business seriously. But looking for a better platform and making sure your team is getting everything out of the current one are two different jobs, and the second one is on us, not the vendor. We are doing both.

Maya Angelou put it better than I can: "when you know better, do better". We know better on three fronts now — what to ask a vendor on the first call instead of the last, what our own statute does to a pricing model built for somewhere else, and what our workflows look like when somebody finally writes them down.

Second chances go both directions on this one.