Their support app seems to function poorly or they may just be understaffed and can't respond or reimburse for other reasons.1.

That's a servicer-side issue, not a function of who's managing the process.

All of his posts still show up as well.

I’m looking for some insight on how to structure an offer on a Fannie Mae REO I’m interested in, especially given some discrepancies in how the property is being represented.Key facts:Current listing: Advertised as a 3 bed / 1 bath at 1,850 sf.Issue: That square footage appears to include a partially finished basement, including a “room” with no proper egress, so it should not be counted as a legal bedroom or finished living area.Prior listing (2021): Previously listed as a 3/1 at 1,572 sf.Fannie/FNMA record: Federal National Mortgage Association currently has it as a 2/1 at 1,368 sf, which is much closer to reality based on what I’ve seen.Pricing history:Sold 7/14/2021 for $450,000.Trustee’s Deed consideration amount: $347,000 dated 10/18/2024.REO list price started at $489,900, then dropped around 2/16/2026 to $484,900.First Look: First Look period expired on 2/20/2026 at 21:00, so investors can now submit offers.My main concerns:The current list price seems to be based on an inflated square footage (counting the basement as living space) and as if it’s a 3/1, when in reality it’s functionally a 2/1 with a partially finished basement.Comps in the area should really be adjusted to the ~1,368 sf, 2/1 configuration, not 1,850 sf, 3/1.Fannie paid effectively $347K (per the Trustee’s Deed), but is trying to list it close to or above what it sold for in 2021, when it was arguably misrepresented then too.What I’m thinking:Have my agent pull comps based on 2/1 and ~1,368 sf only, ignoring the basement as finished living area, and value the property that way.Back into my maximum offer using:ARV for a 2/1 at ~1,368 sf.Less repairs/updates needed.Less my desired profit and holding costs.Use the misrepresentation of square footage and non‑egress “bedroom” as leverage, both in the initial offer and during any inspection/renegotiation.Questions for the community:For those who have bought Fannie Mae REOs recently, how aggressive can I realistically be on price once First Look has expired?

If you click there, a short drop-down is revealed with Forums as one option. 

Sometimes it’s layout, functional obsolescence, deferred maintenance, or simply buyer pool depth at that price tier. 

AI can't write property descriptions at all and those who use it are going to fall back in the pack because the algorithms can recognize it.

Keeping renovations simple, clean, and functional also helps maximize return on investment.

Aiming for 6% all-cash in A / A- / strong B+ Midwest neighborhoods isn’t crazy at all when the goal is durability, low stress, and predictable income rather than max IRR.

We tested Monday and ended up building our ops around ClickUp as the system of record, with our PMS and automations feeding it.How we run STR ops (high level)PMS drives the truth (reservations, changes, cancellations).Automation pushes events into ClickUp so humans work from tasks, not inboxes.For example: Guesty → webhook → database layer → create/update ClickUp tasks for inquiries + reservations, with custom fields like check-in/out, guest, listing, status, conversation links, etcWe also automate “edge-case ops” like pool heat, early check-in, late checkout, pets, extra guests by generating subtasks/checklists off a request.Where Monday tends to feel greatFast to set up boards, very visual.Good for simple pipelines: turns, maintenance queues, onboarding checklists.Dashboards and “who owns what” is easy for teams that hate complexity.The biggest hurdles / limitations people hit with Monday in STR (in my experience)When the PMS needs to be the source of truthSTR is event-driven: reservation updates, cancellations, date changes, channel messages.If Monday is the “truth”, you end up reconciling drift constantly.Automation ceilingMonday automations are solid for basic triggers, but once you want “if X then create Y tasks, keep them in sync, dedupe, move between pipelines, update 15 fields, attach links”, you start wanting a real workflow engine + database.Data model constraintsSTR ops has “objects”: Reservation, Property, Guest, Work Order, Vendor, Owner, Conversation.Monday is board/item-first, so relationships can get awkward at scale unless you build a lot of glue.High-volume operational noiseHundreds of small updates (date changes, guest count changes, messaging, payments, add-ons) can turn boards into a scroll-fest unless you are very strict about what becomes an item vs a log.If someone is committed to Monday, this is the way I would set it upBoards by function, not by property:Reservations pipeline (pre-arrival, in-house, checkout, post-stay)Turns and housekeepingMaintenance and inspectionsOwner requests and approvalsOne unique ID field per reservation and treat it like a primary key.Use an integration layer (Zapier, Make, n8n, custom) so the PMS updates Monday automatically, not manually.Bottom lineMonday is awesome if your ops are mostly human-driven and you want speed + visibility.