Firms that sell hours still run on intake and a shared drive

We work with firms that sell hours: law, accounting, consulting, architecture, agencies, and clinics that run on appointments. The person we sit with can open last month’s intake spreadsheet, last week’s proposal folder, or the shared mailbox that is the real CRM. They know which matter started from a web form that asked the wrong question. They know which proposal reused a stale rate card. Cyriac Zeh founded Nidrosoft in San Diego to put those packets into systems the firm already owns. If you sell a physical product and hours are a side note, the e-commerce or manufacturing pages are a better door.

A normal Monday at a mid-size firm looks like this. Three inquiries arrived over the weekend. One is a conflict you will not know until someone searches a list. One is a price shopper who wants a number in the first email. One is a real matter with a deadline and a missing document. The intake coordinator forwards all three to a partner. The partner is in a hearing or a workshop. By Tuesday the real matter has hired someone else and the price shopper is still in the inbox. That Monday is the work. We map it before anyone talks about an associate chatbot.

Utilization is already on a dashboard. The hours that do not show are the ones spent hunting a prior proposal, rewriting a scope someone already approved, and answering “did you get my email” from a client who attached the file to the wrong thread. Partners call that business development. Coordinators call it the job. We call it a queue with an object: the inquiry, the conflict check, the proposal, the engagement letter, the first work plan. If you cannot name the object, you are buying a toy. If you can, we have a method.

We are the wrong seat when you want a practice-management replacement for every firm type, a billing engine, or an unattended outbound machine that impersonates a partner. We are the wrong seat when the only approved project is a keynote. If you want ChatGPT seats for associates, buy seats and a policy on what may be pasted. If you want intake that cannot create a matter without a conflict check, and a proposal a partner still sends, keep reading and then use /services/audits.

Intake is a filter, not a welcome mat. A web form that asks for a name and a story will fill the mailbox and starve the calendar. The questions that matter are the ones the firm already knows: who is adverse, where the work sits, what the deadline is, what document is missing, whether this is a client you already have. Coordinators ask those questions by phone after the form fails. We put the questions on the form and on the follow-up draft. A person still decides whether the firm wants the work. Software that “accepts the client” is how you get a conflict letter from the other side.

Conflict checks are a search problem with a liability attached. Names are spelled wrong. Companies have parents. A spouse appears later. The list lives in the practice system, a spreadsheet, and a partner’s memory. We do not replace your conflicts database. We refuse to open a matter in the pipeline until the check has a result and a name on it. If your system cannot search, the first build may be a better search, not a model. That is an operational finding. It is also cheaper than a motion you will not enjoy.

Document collection is a chase. IDs, tax packets, prior agreements, medical charts, a lease, a cap table. Clients send a photo of page two. The coordinator asks for page one. Three days pass. The partner asks why the file is empty. We attach a checklist to the inquiry, we draft the chase with the missing item named, and we leave the “we cannot start until” sentence with a human. A model that starts drafting advice from page two is a malpractice story. We will not ship that story as a feature.

Routing is politics as much as process. Some matters go to a practice group by keyword. Some go to the partner who golfed with the referrer. Some go to whoever has capacity, which is a rumor. We write the written rule and the exception. A draft can propose a route. A named person still assigns. If the firm will not name that person, intake automation will become a second fight. We would rather lose the project than install a router nobody will honor on a Friday.

A proposal is a packet: problem, scope, what is out, who does the work, rate or fee, timeline, and assumptions. Firms rebuild it from the last PDF that was “close enough.” The rate card has changed. The assumption about client data has changed. The out-of-scope list has not, and that is how you eat a month. We treat the proposal as a generated draft over a live rate card and a live out-of-scope list. A partner still sends it. A model that invents a fee the firm does not offer is a write-off waiting for a kickoff.

NanoBrief is a live Nidrosoft system for the brief that sits in front of that packet. It asks a short, industry-specific questionnaire and drafts a usable brief in under two minutes, against the three-plus hours that document often takes. Templates exist for marketing, design, video, legal, and other desks. A consultant or an agency lead can share a link without forcing the client to create an account to read it. Export to PDF or Word is there when the firm still lives in attachments. We will not claim NanoBrief is a full proposal engine for every partnership agreement. We will claim it stops the brief from starting as a blank page.

Scoping conversations fail when the brief and the proposal disagree. The client said “phase one only.” The PDF still lists phase two as optional in a way that looks included. The kickoff becomes a fight. We keep the brief object next to the proposal object so a change in one flags the other. A human still decides which document wins. If your firm sells a fixed fee with a fuzzy scope, the first finding of the audit is the fee, not the model. Software will not save a price you cannot defend.

Engagement letters and outside counsel guidelines are a later slice. Some clients send a thirty-page set of rules about staffing, billing increments, and tools. Associates already ignore the PDF. We can extract the rules the matter must see (no certain models, no offshore, a billing increment) and put them on the file. We will not pretend we negotiated the guidelines. We will not let an agent paste client facts into a consumer tool those guidelines already banned. That ban is a product requirement, not a suggestion in a workshop slide.

Firms buy workshops when five partners have five stories about what AI is allowed to do. One wants a bot on the website. One wants associates faster. One wants nothing pasted anywhere. The room is a fight dressed as education. Nidrosoft’s corporate AI training uses a real intake, a real proposal, or a real internal memo the firm already redacted. Leadership sees what a model can draft and what a person still has to sign. Teams leave with a playbook. We do not leave with your files on a laptop we keep.

A half-day that works has a live tool the firm already pays for, a packet the coordinator recognizes, and a decision at the end: audit, build, or stop. A half-day that fails is a model zoo and a slide about the future of the profession. We will not run the second one. If you need a keynote for a retreat, hire a speaker. Cyriac Zeh has sat on San Diego executive roundtables. That is a different product. This page is for the room that will open the inbox after lunch.

Engineer and operator tracks differ. Associates need a pattern for research drafts and a ban list. Coordinators need the intake checklist and the chase email. Finance needs the rate card and the write-off. We split the room when the firm is large enough that one talk will waste two hours of someone’s time. We keep the rooms honest about paste risk. A workshop that does not mention what may not go into a consumer box is a workshop we will not put our name on.

Workshops are enough when alignment is the problem and the packet is not yet counted. They are not enough when intake already loses matters on Tuesday and the proposal already lies about scope. We will say which side you are on in the first call. Buying training to avoid a build is fine when the firm is not ready. Buying training to look ready is a waste of a Monday. We would rather you wait.

The matter inbox is a status machine. Clients ask whether you received the document. Associates ask where the prior memo lives. The other side sends a letter that should have started a clock. Most firms run this in Outlook with folders that die when someone goes on leave. We open that mailbox in the audit. We count which threads are status, which are new work, which are billing questions, and which are documents that should have landed in the matter file. That count decides whether the first build is routing or a better file.

Time entry is a memory test at 6 p.m. Associates reconstruct the day from sent mail. Partners write “attention to matter” and hope it passes. Clients reject lines. The firm already has rules about increments and verbs. We can draft time entries from a calendar and a sent folder the associate still edits. We will not invent hours. We will not ship a silent padder. If your realization problem is a price problem, the audit will say so. A drafted narrative will not save a rate the client already refused.

The shared drive is still the DMS in more firms than the brochure admits. Version 7 of a memo sits next to version 3. The signed letter is in an email. The exhibit is on a laptop. We do not need to replace iManage or a SharePoint you already hate on day one. We need a rule that a proposal, a letter, or a filing cannot be marked sent unless the file has a place and a name. That rule is boring. It is also how you stop sending version 3 to a client who has version 6.

Research drafts are the associate use case everyone wants and the paste case everyone underestimates. A model can outline a memo. A person still cites and still decides. Client facts do not go into a consumer box if the engagement or the bar says they do not. We build in the accounts the firm already approved. If the firm has no approved account, the first recommendation is that account and a policy, not an agent. We have no interest in a demo that pastes a client letter into a public chat to look fast.

Embed means we sit with the coordinator and the partner who actually opens the weekend inquiries. We watch a conflict search fail. We watch a proposal get copied. We take the practice-system and mailbox access they already have, under their policies. We do not start with a lecture about agents. The first week is access, shadowing, and the list of packets. The longer path is on /how-we-work. Cyriac Zeh ships that path under the name The AI Architect. Nidrosoft is the studio that invoices.

Diagnose means we cost the repeating work. Hours on intake chase. Hours on proposal rewrite. Matters lost after a weekend. Write-offs from a fuzzy scope. We score whether we can reach the practice system, the mailbox, and the rate card. A firm that will not show a redacted inquiry log cannot buy an intake project in good faith. We will say that in week one rather than invent a conversion rate.

Scope means you buy a result. For intake, a complete packet, a conflict result, and a human assignment. For proposals, a draft over a live rate card and a partner send. For training, a playbook on your tools. We refuse “AI for the firm.” If you cannot name the packet, you are not ready. If the packet is a filing or a fee, the human stays in the sentence. We will walk if you delete that sentence.

Build means we ship into your stack. Clio, PracticePanther, a custom matter system, Outlook, a shared drive: the ones you name. Your people sit with us while the first live draft goes to a small slice of inquiries, then the slice grows. Someone in-house has to be able to edit the checklist and pause a send on a Friday. That person is part of the build. Twelve-plus years of product work has made us impatient with a vendor-only admin.

Own means the credentials, the rate card, and the approval policy stay yours. We maintain what you ask us to maintain. We stay out of the rest. If a client guideline changes the ban list, the owner of the matter is you, and we update the rule with you. Continuous work is fewer empty files on Tuesday and fewer proposals that lie about scope, measured in the queues you already run. If those queues do not move, we say so and we stop expanding the slice.

Do not hire Nidrosoft to practice law, medicine, architecture, or audit. We will not file, diagnose, stamp, or sign. Eviction Wizard holds a housing file from notice to writ and still leaves the filing with a human. Omnira Dental leaves the chair with the dentist. Your firm’s license is yours. A partner who wants a button that “does the memo” and sends it is asking us to put our name under theirs. We will not.

Do not hire us to replace the practice-management system as a first project unless the system cannot search conflicts and that is the actual fire. Migrations eat years. Most firms need a packet on top of what they already pay for. If a vendor is blocking an API, we say so in week one and we design around export plus a human paste. We will not sell a new platform so a demo looks clean.

Do not hire us for unattended outbound that impersonates a partner, or for a website chatbot that quotes a fee. Fees and advice are writes that cost the firm. A named human sends them. If your marketing lead wants a bot that always books a call and always names a price, hire a different shop. The same no applies to pasting client facts into a consumer tool the guidelines already banned.

We are a poor fit for a retreat keynote with no packet, and for a two-person shop that wants “AI transformation” as theater. Nidrosoft’s main seat is an operator with a repeating inquiry and a decision maker in the room, often 30 to 250 people, sometimes smaller when one intake queue pays for itself. A solo can still write. We will tell you if NanoBrief or a half-day is enough, or if you should keep the shared mailbox for another season.

An AI audit is two weeks in the work. We take a redacted inquiry log, a sample of proposals, and a week of the shared mailbox. We sit with the coordinator, a partner, and whoever owns the practice-system admin. We write down every handoff: who searches conflicts, who drafts the first reply, who edits the rate, who sends. The deliverable is a ranked map and a list of things we will not touch. Details live on /services/audits.

Access is the gate. Practice system, mailbox, rate card, and a redacted matter sample if time or research is in scope. We use your accounts and your policies. We do not ask you to paste client letters into a consumer chat so we can “try a prompt.” If counsel or the partnership needs a DPA, we do that first. If conflicts data cannot leave the building, we work in the building’s tools. That constraint is normal. We will not fight it for a nicer screenshot.

We score failure the way the partnership scores it. A missed conflict is a motion. A weekend inquiry that died is a lost matter. A proposal that included phase two by accident is a write-off. A memo sent from version 3 is a client call you will not enjoy. Those outrank a slightly nicer first email. Sometimes the first recommendation is a checklist and a required conflict field, with no model in the loop. That is a successful audit. You still own the map.

At the end you get a build order you can take to another shop. If the first line is “use NanoBrief for the brief and keep the partner on the send,” we write that. If the first line is “buy an approved account and a paste policy, not a build,” we write that too. The audit is the product. The build is a separate buy. Start at /contact or send cyriac@nidrosoft.com a redacted weekend of inquiries.

Healthcare is the closest sibling because Omnira Dental is live and the chair is already a professional hour. Real estate is next because Eviction Wizard is live and many firms sit on those files. We will not tell a consulting shop that a notice form is their product. We will tell them we already built a packet with a clock and a human on the commit. FinTech transfers Protectron: EU AI Act drafts that counsel still reviews. TokenTra transfers the meter if the firm has already given every associate a key and the bill has no owner. Ten to 30 percent wasted spend is the published range when features have names.

E-commerce transfers inbox routing and the honesty that we do not have a flagship storefront. Agencies that sell hours and also run ads will recognize NanoBrief and Octana (one message in, a finished video out). We still will not call Octana a professional-services platform. Automotive transfers the overnight queue: Nexuvo messages sellers while the lot is closed, with a human on the buy. A firm can use the same pattern on after-hours intake drafts. A partner still sends anything that looks like advice or a fee.

Software and venture pages are for product teams and funds. A firm that is building a product on the side can read those. A firm that is only selling hours should stay here. Music tools (Clear Audio AI, MixGuidera) matter if the practice is audio. We will not force them into a tax shop. The sibling list exists so we can send you to the right door instead of stretching one story over every partnership.

Write cyriac@nidrosoft.com with a redacted weekend of inquiries, a proposal you had to rewrite, or the workshop fight you keep having. Name the practice system, the mailbox, and the person who can send a fee. Cyriac Zeh reads that mail from San Diego. We will tell you whether the next step is NanoBrief, Omnira Dental (if you are a practice), a two-week audit, a half-day, or a no because you need a law firm or a PM vendor, not us. We do not need a brand film.

If you already want the ranked map, book the audit on /services/audits. Two weeks, your accounts, your people, a build order you can take elsewhere. If you already know intake is the fire, say so in the first line. If proposals are the fire, say that. If the fire is a partner who pastes client letters into a consumer box, say that so we can talk about an approved account before we talk about chrome.

If the fire is alignment, book training. Corporate AI training at Nidrosoft uses your packet. The playbook stays. If the fire is a live clinic, open Omnira Dental. If the fire is a housing file you already run, open Eviction Wizard. We would rather you use a live system than buy a custom build you do not need. That sentence is how we stay in business without inventing a suite for every profession.

Nidrosoft is twelve-plus years of product work in a studio that still answers mail. 125 products. 16 public systems. The professional-services proof is NanoBrief on the brief, Omnira Dental on the chair, workshops on your tools, and custom intake on the system you already pay for. If that mix matches the desk you run, write us. If it does not, use the sibling pages or go back to the shared mailbox. Both are honest endings.