Notices, listings, and the inbox that actually runs the building

We work with property managers who still build pay-or-quit packets in Word, listing coordinators who paste remarks into the MLS by hand, and eviction desks that track service dates in a shared sheet. The company can be a single-market manager with a few hundred doors or a brokerage whose listing desk already has a queue. What we need is a person who owns the file, a workflow that repeats every week, and login access to the property system, the inbox, or the case tracker. Cyriac Zeh founded Nidrosoft in San Diego to sit in that seat, not to pitch a generic chatbot to a board that will never open the lease.

A typical morning on a residential book looks like this. Rent posts overnight. The PMS flags units past the grace period. Someone exports a list, opens last month’s notice template, and types the tenant name, the unit, the balance, and the deadline. They print, they email, or they hand the PDF to a process server. If the address line is missing a unit letter, the clock restarts. If the ledger and the notice disagree by fifty dollars, the attorney sends it back. That packet is the first place we look, because the steps are already known and the cost of a bad notice is a reset, not a slightly slower email.

On the sales side the repeating work lives with the listing coordinator. A new listing arrives as a folder of photos, a seller worksheet, and a remarks draft that still says “spacious” three times. The coordinator resizes images, writes the public remarks to the character limit, sets the showing instructions, and pushes status from coming soon to active. Portals lag. Price changes sit in a draft. The agent texts from a showing and asks whether the lockbox code went out. We map that desk the same way we map a notice desk: one packet, one owner, one system of record.

We are the wrong seat when the only ask is a prompt library for agents who will not change how they write offers. We are the wrong seat when counsel wants a national eviction product that practices law in fifty states from a San Diego laptop. We are the wrong seat for a board-only strategy mandate with no build and no named operator. If you want ChatGPT seats and a lunch-and-learn, buy the seats. If you want a system that drafts the notice, tracks service, and leaves the filing decision with a human, keep reading and then book the audit at /services/audits.

Notice work is a clock. Three-day, five-day, ten-day, thirty-day, and sixty-day forms pull different lease clauses and different service rules. The person doing the work has to match the tenant legal name to the lease, the balance to the ledger, and the address to the unit that the sheriff will actually find. They also have to record how the notice went out: posted, mailed, emailed, or handed to a server. Most shops store that proof in a folder named for the month. When a hearing date appears, someone hunts for the PDF. We cost that hunt in hours before we talk about models.

Listing work is a packet with a public face. Photos have an order. The first frame is the one portals will crop. Remarks have a hard character count. HOA documents, seller disclosures, and the lockbox code live in three different threads. A coordinator who handles twenty actives a week spends the first hour of the day answering “is this live yet” from agents who already told the seller it would be up last night. Status changes (coming soon, active, pending, withdrawn) have to hit the MLS and then the syndication feed. When they do not, the public listing lies and the next showing is a fight.

MLS work is license work. IDX and VOW rules decide what a public site can show. A field that looks harmless in the office worksheet (a tenant-occupied flag, a seller concession, a showing instruction) can be required, optional, or forbidden on the public side. Coordinators keep a mental map of which remarks belong in public, which belong in private agent remarks, and which belong in an email that should never hit the listing. We treat that map as part of the system. A model that dumps the whole worksheet into public remarks will get the brokerage in trouble faster than a slow coordinator.

The inbox is the fourth queue and it never closes. Tenants write about a leak. Buyers ask for a second showing. Vendors send invoices with no unit number. An agent forwards a thread that already has fourteen replies and no decision. Most teams run this in Gmail or Outlook with a shared mailbox and a naming scheme that lasts until the first vacation. We open that mailbox in the first week. We count how many messages are status questions, how many are repair intake, and how many are documents that should have landed in the PMS or the listing folder. That count decides the first build.

Nomerlo is a property search product Nidrosoft already shipped. A visitor filters by price, beds, and map, opens a gallery, reads neighborhood notes, saves a search, and contacts an agent. That is the public side of listing work. The private side is the coordinator packet: photos in the right order, remarks inside the limit, showing instructions that match the lockbox, and a status that the MLS will accept. We name both sides because a pretty search page that reads stale MLS data is a complaint, and a perfect MLS row that never reaches a usable public page is a wasted listing.

Photo work has a sequence most teams skip writing down. Exterior first, then the room the seller cares about, then the rest, with the worst closet last. Portals crop the first frame. A vertical phone shot becomes a square and the house looks like a hallway. Coordinators already know this. They still spend a morning renaming IMG_4033 and dragging files in an MLS uploader that times out. A build here is boring on purpose: a checklist, a required first frame, a rejection when the file is too small, and a place the agent can see that the gallery is ready before they text the seller.

Remarks are a writing job with a compliance job taped to it. Public remarks cannot promise a school, invent square footage, or copy a fair-housing problem from last year’s template. Private agent remarks hold the alarm code and the dog note. We have watched desks paste the seller worksheet into both fields because the form had one comments box. The fix is a split draft with a character count and a short list of phrases the brokerage already banned. A model can propose the public paragraph. A coordinator still hits publish. That split is the product, not a magic listing writer.

Syndication is where status lies. The MLS says pending. Zillow still says for sale. The showing inbox fills with people who will be angry at the door. Someone on the desk already knows which portal lags and which field the feed drops. We write that down in the audit. We do not promise we will replace your MLS vendor or your IDX license. We can draft the status change, queue the portal ticket, and tell the agent what the public page still shows. If your only problem is a bad IDX contract, call the vendor. If your problem is a desk that cannot see the lag, we have a job.

A property inbox is a mix of emergencies and paperwork. A tenant sends a photo of a stain and no unit number. A vendor replies to a work order from 2023. An applicant uploads a pay stub to the wrong address. The person who owns the mailbox already has rules in their head: after-hours leak goes to the on-call, cosmetic paint waits for make-ready, anything about a notice goes to the eviction desk, not to the leasing agent. Those rules rarely live in the PMS. They live in a person. We sit with that person and write the rules as routing, not as a slogan about customer experience.

Showing mail is a calendar problem dressed as hospitality. A buyer agent asks for 4:15. The listing says two-hour notice. The seller is on a flight. The lockbox code changed yesterday and only one coordinator has the new one. Confirmations go out late, so two cars arrive at 4:10 and the neighbor calls. We treat this as a queue with constraints: notice window, occupancy, pet, and code owner. A draft reply can hold the slot and the code path. A human still sends it when the seller has not approved the window. The gain is that the constraints are on the file before the reply, not in a text the coordinator sent from a showing.

Application packets are another inbox species. Credit, income, IDs, and pet letters arrive as five attachments with five file names. Screening tools already exist. Teams still download the zip, rename the files, and upload them to the PMS because the screening email and the unit record do not talk. We do not replace your screening vendor. We attach the packet to the unit, flag the missing ID, and leave the approve-or-deny decision with the person who already has that authority. If your state has a fair-housing clock on applications, that clock belongs on the same record as the attachments.

Vendor threads are where money hides. A plumber invoices a unit that was vacant, then occupied, then vacant again. The invoice has a street address and no unit. Accounts payable asks the manager. The manager asks the inbox. Two weeks later the invoice is paid against the wrong owner. We tag the thread with a unit and a work-order number before anyone talks about an agent that “handles vendors.” The first build is often a parser that refuses to file an invoice without a unit. That sounds small. It is the difference between a clean owner statement and a monthly argument.

Omnira is Nidrosoft’s agentic platform for traditional industries. Omnira Dental is live for practices. Omnira Real Estate is in build. Omnira UI is the open-source design system under those products. We say this in the open because buyers search for a finished real estate suite and we will not sell them a dental product with the logo swapped. If you need a live eviction path today, Eviction Wizard is the public system. If you need a public listing search, Nomerlo is the public system. If you need a broader agentic layer across listings, notices, and inbox, that is the Omnira Real Estate work, and it is not shipped as a product yet.

In-build means we are still deciding which objects the vertical must own: the unit, the listing, the notice, the showing, and the inbox thread. Dental already taught us that a vertical dies when it pretends a “conversation” is the record. A tooth has a chart. A unit has a lease and a ledger. We are not porting dental agents onto houses. We are taking the same platform habit (a record, a human approval on writes that move money or legal rights, an audit trail) and fitting it to property files. Until that ships, custom work for your PMS and your mailbox is the path we sell.

Cyriac Zeh ships that platform work under the name The AI Architect. Nidrosoft is the San Diego studio. The practice is one person who can hold design, engineering, and the live system in the same week. Before the studio he worked at Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. The real estate work still starts on a desk with a printer and a PMS, not in a lab. If you want a large account team and a twelve-week discovery deck, hire a firm that sells that. If you want the person who shipped Eviction Wizard in the room with your coordinator, write us.

Embed means we sit with the person who already runs the packet. On a notice desk that is the coordinator who opens Word at 8:40. On a listing desk that is the person who owns the MLS login. We watch them pull the lease, the ledger, the photo folder, and the last email from the agent. We take notes in their language: three-day, make-ready, coming soon, lockbox. We do not start with a workshop about large language models. The first week is access, shadowing, and a list of the systems that already hold the truth. Read the full path on /how-we-work.

Diagnose means we cost the repeating work. How many notices go out in a normal week. How many get redone because the balance was wrong. How long a listing sits in “photos received” before it is active. How many inbox threads are status questions that the PMS could have answered. We score each queue on hours, on the damage when it fails, and on whether we can reach the system of record. The output is a ranked map, not a vision deck. The first item is usually the packet that already has a known happy path and a known failure, like a notice that restarts the clock.

Scope means you buy a result. We pick one queue. We write what the system will draft, what a person must approve, and what “done” looks like in the PMS or the case file. For notices, done might be a packet with matching ledger, a service method, and a next date, sitting in Eviction Wizard or in your own tracker. For listings, done might be a remarks draft, a photo order, and a status the coordinator still publishes. We refuse a scope that says “AI for the whole company” with no file attached. If you cannot name the packet, you are not ready to buy a build.

Build means we ship into the stack you already run. Propertyware, AppFolio, Yardi, a brokerage CRM, Gmail, a shared drive: we work in the ones you name. We do not ask a mid-market manager to migrate doors to a new PMS so our demo looks clean. Your people sit with us while the draft, the approval, and the write-back go live. Someone in-house has to be able to explain the system on a Friday when we are not on the call. That person is part of the build, not a training add-on at the end.

Own means the system was yours from the first login. Credentials stay in your accounts. Policies stay yours. If a region requires EU hosting, we use it. We stay on for the pieces you want maintained and we stay out of the rest. Continuous work is measure, fix, and add the next queue, not a retainer that quietly becomes staff aug with no owner. Nidrosoft has shipped 125 products and keeps 16 public systems in the archive so you can see what “own” looks like when the studio is the one on the hook.

Do not hire Nidrosoft to replace your MLS. We will not build a new multiple listing service, an IDX network, or a data license that competes with the association you already pay. Coordinators hate the uploader. That is real. The cure is almost never a new MLS. The cure is a packet that is complete before anyone opens the uploader, and a status check after syndication. If your board wants a statewide listing utility, that is a consortium project with lawyers and a decade. We build the desk that has to live with the MLS you have.

Do not hire us to practice law. Eviction Wizard holds a file from notice to writ. It does not give legal advice, pick a cause of action, or file in a court where you have no counsel. A property manager who wants a button that “does the eviction” without an attorney is asking us to break the thing that keeps them employed. We will say no. The same no applies to fair-housing copy, habitability decisions, and any write that starts a lockout. Those stay with a named human. If that sentence bothers you, we are a bad match.

Do not hire us for a chatbot that sits next to the PMS and answers “what is my rent” from a brochure. Tenants already have a portal. Agents already have a phone. A chat window that cannot see the ledger, the notice, or the showing calendar becomes a second inbox. We have watched teams buy that window and then staff it. If your only approved project is a widget on the marketing site, hire a web shop. If you want the widget later, we can talk after the file is clean.

We are also a poor fit for a single agent who wants a personal brand engine and no operations owner. Nidrosoft’s main seat is a company with a repeating packet and a decision maker in the room, often in the 30 to 250 person range, sometimes smaller when one build pays for itself. A solo agent can still write cyriac@nidrosoft.com. We will tell you quickly if a workshop or a short audit is enough, and we will tell you if you should just use the tools you already have. Flattery is not a service we sell.

An AI audit at Nidrosoft is two weeks in the work. We take a sample of notices, a sample of listings, and a sample of inbox threads. We sit with the coordinator, the manager, and whoever owns the PMS admin login. We write down every handoff: who exports the delinquent list, who edits the template, who calls the server, who updates the MLS, who answers the showing text. The deliverable is a ranked map with a first build, a set of things we will not touch, and a plain cost in hours. Details live on /services/audits.

Access is the first test. If we cannot see a redacted lease, a redacted ledger, and a week of the shared mailbox, we cannot rank the work. We use your accounts and your policies. We do not ask you to dump tenant files into a consumer chat product so we can “try a prompt.” If your counsel needs a DPA, we do that before we open the box. If your PMS vendor blocks API access, we say so in week one and we design around export and a human paste rather than pretending a blocked API is a strategy problem.

We score failure the way a hearing scores it. A wrong balance on a notice is a reset. A public remark that implies a school is a compliance event. A lockbox code in public remarks is a break-in waiting for a screenshot. A missing service affidavit is a continuance. Those failures outrank a slightly slower email every time. The audit will sometimes tell you the first build is a checklist and a required field, with no model in the loop. That is a successful audit. You still own the map.

At the end of the two weeks you get a build order you can take to another shop. Nidrosoft would rather lose the implementation than trap you in a slide only we can decode. If the first item is “use Eviction Wizard for the notice desk,” we will say that. If the first item is “stop pasting the seller worksheet into public remarks,” we will say that too, even if it does not need us. The audit is the product. The build is a separate buy. Start from /contact or write cyriac@nidrosoft.com with the packet you hate most.

Healthcare is the closest sibling because Omnira Dental is live and the real estate vertical sits on the same platform family. A dental chair has a chart, a payer, and an intake form. A unit has a lease, a ledger, and a notice. The habit that transfers is the record: a write that changes money or legal status needs a human, and the system has to show who approved it. We will not tell a property manager that a dental agent can run their book. We will tell them we already learned what happens when the conversation is treated as the source of truth.

Automotive transfers the overnight queue. Nexuvo dealers pull private-party cars from Facebook, Craigslist, and Cars.com while the lot is closed, and they acquire three times the inventory with eighty percent less manual outreach. A listing desk is not a car lot. The transfer is the idea of a night job that drafts outreach and leaves the commit for morning. A property shop can use the same pattern on stale listings, expired seller follow-up, or vendor bids that arrive after 6 p.m. The human still sends the message that starts a legal or money path.

Professional services transfer the legal desk. Eviction files often sit next to a firm that sells hours. Intake, a caption, a deadline, and a human who will not let software file the paper: that is the same discipline we write about on the professional services page. FinTech transfers the approval habit. TokenTra and Protectron are public systems for token bills and EU AI Act documents. We are not a bank and we will not move owner funds. We will put a human on any write that looks like money. Manufacturing transfers the floor habit: the spreadsheet that still runs the shift, which in property is often the make-ready board.

The fastest start is a redacted notice that went wrong, a listing that sat in draft for a week, or a forwarded mailbox thread that has no owner. Put that in an email to cyriac@nidrosoft.com and name the system of record: the PMS, the MLS, the case tracker, or the shared inbox. Cyriac Zeh reads that mail from San Diego. We will tell you whether the next step is a two-week audit, a hard no, or a conversation about Eviction Wizard as it already runs. We will not ask you for a 40-page RFP before we have seen a file.

If you already know you want a ranked map, book the audit. Two weeks, your accounts, your people, a build order you can take elsewhere. If you already know the notice desk is the fire, say so. If the listing desk is the fire, say so. If you want Omnira Real Estate when it ships, say that too, and we will keep you on the honest side of “in build.” Do not ask us to mark a dental product as a property product so a slide looks finished. We will refuse.

Workshops exist when the company is not ready to buy a build. Corporate AI training at Nidrosoft uses your MLS packet or your notice template, not a toy dataset. Leadership sees where a model can draft and where a person still has to sign. Teams leave with a playbook. A workshop is enough when the real problem is that five people have five stories about the same file. A workshop is not enough when the file is already clear and the hours are already counted. We will say which side you are on.

Nidrosoft is twelve-plus years of product work compressed into a studio that still answers a shared inbox. 125 products shipped. 16 public systems. The real estate proof is Eviction Wizard on the eviction path, Nomerlo on search, and an Omnira vertical that we will not announce as live until it is. If that mix matches the desk you run, write us. If it does not, the sibling pages on this site will send you to a better door, or you can close the tab and go back to the packet. Either outcome is fine with us.