# Azkosoft > Azkosoft builds custom software, AI agents and AI voice systems for businesses that have outgrown spreadsheets and off-the-shelf tools. Working with teams worldwide. This is the long briefing. The short index is at https://www.azkosoft.com/llms.txt. ## Who this is Azkosoft builds custom software, AI voice agents, AI agents and automation, mobile apps, integrations, and SaaS platforms for businesses that have outgrown spreadsheets and off-the-shelf tools. Common trades: hotels, schools, clinics, engineering and trades, retail and wholesale, restaurants. Buyers are worldwide. Rules that are true today and must not be invented around: - No public client names. The work at https://www.azkosoft.com/work is concept builds using invented company names, each labelled as such. - No published prices, day rates or guaranteed timelines. - No office address, phone number, team size, certifications or star ratings. - You own the source, the data and the accounts (hosting, domain, app stores, AI providers). - If an off-the-shelf tool would do the job cheaper, that is the honest answer. Contact: hi@azkosoft.com — https://www.azkosoft.com/contact ## Services ### Custom Software When spreadsheets stop coping and off-the-shelf software almost fits but not quite, we build the thing that fits. Booking systems, job tracking, inventory, admin portals, customer dashboards -- whatever the daily work needs. URL: https://www.azkosoft.com/services/custom-software What you get: - A working system, not a prototype: Deployed on your own domain, with your data, backed up, and usable by your team on day one. Not a demo you have to rebuild later. - Roles and permissions: Owners see everything, staff see their own work, and part-time people see only what they need. Set up once, changeable later without a developer. - Reports people actually open: The three or four numbers your week runs on, on a screen, current. Plus CSV and PDF export for the accountant. - Your existing data, moved in: We import what is in the spreadsheets and the old system so you start with history, not an empty database. - Documentation and handover: Written guides for your team and the full source code. You can take it to another developer at any point. Q: How is this different from buying software off the shelf? A: Off-the-shelf is cheaper and faster when it fits. It stops being cheaper when your team spends an hour a day working around it. We build custom when the gap between how the tool works and how you work is the expensive part. Q: What happens to our spreadsheets? A: They get imported. Years of history come with you, and the spreadsheet stays as a read-only archive until you are confident in the new system. Q: Do we own the code? A: Yes. You own the source, the data and the accounts it runs on. There is no lock-in and no per-seat licence to us. Q: What if we need changes after launch? A: Most clients keep us on a small monthly arrangement for changes and fixes. Others take the code in-house. Both are fine and we set it up so either is possible. ### AI Voice Agents A voice agent picks up when your team cannot -- after hours, during the rush, on a public holiday. It answers common questions, takes a booking or a message, and passes anything unusual to a person with the full context of the call. URL: https://www.azkosoft.com/services/ai-voice-agents What you get: - A number that always answers: Your existing number, forwarded, or a new one. It picks up on the first ring at 2am on a bank holiday. - Answers written by you, not guessed: The agent works from your real information -- hours, prices, rooms, menu, policies. It says "let me put you through" instead of inventing an answer. - Bookings written into your system: A reservation taken on the phone lands in the same calendar or booking system your staff already use. No retyping. - Handoff to a human, with context: Anything unusual, angry or high-value goes to a person, and that person gets a summary of what was already said. - Transcripts and call analytics: Every call recorded, transcribed and searchable. You find out what people actually ring about, which is usually a surprise. - Outbound calls too: Appointment reminders, no-show follow-ups and confirmation calls, on a schedule. Q: Will callers know it is not a person? A: It says so at the start. Trying to pass a machine off as a person is how you lose trust, and in some places it is illegal. In practice people mind far less than owners expect, as long as it is fast and gets them to a human when they ask. Q: What happens if it does not understand? A: It hands over. The rule we build to is that the agent never guesses at anything involving money, medical detail or a complaint. Q: Which languages? A: The common ones are handled well -- English, Spanish, French, German, Arabic, Hindi and more. It answers in whatever language the caller opens with. Q: Can it work with the phone system we already have? A: Usually, yes. It sits in front of your existing number by forwarding, so nothing changes for your callers and you can switch it off in a minute. Q: What does it cost to run? A: There is a build cost and a per-minute running cost. The running cost is normally a small fraction of a part-time receptionist, but we give you the real numbers for your call volume before you commit. ### AI Agents & Automation Invoices that need reading, forms that need sorting, enquiries that need a first reply, reports that get rebuilt every Monday. We build agents that do the first pass and flag only what needs a human. URL: https://www.azkosoft.com/services/ai-automation What you get: - Document reading that handles the messy ones: Invoices, purchase orders, delivery notes, handwritten forms, photographed receipts. Extracted into structured data, with a confidence score so you know what to check. - An answering agent that only uses your content: It answers from your policies, manuals and past tickets, and links to the source. If the answer is not in your material, it says so rather than improvising. - Enquiry sorting and first replies: Incoming email and form submissions read, categorised, routed to the right person, and drafted with a reply your team approves before it sends. - The weekly report, rebuilt on its own: Pulled from the systems it lives in, generated on schedule, in your inbox before the meeting. - A review step you control: You choose what runs unattended and what waits for a human. We default to caution: anything touching money, health or a contract gets reviewed. Q: What if the AI gets it wrong? A: It will, sometimes. That is why we build a review step and a confidence score into anything that matters, and why we run it silently alongside your team first. You see the error rate before you rely on it. Q: Does our data get used to train someone else's model? A: No. We use business API tiers that exclude your data from training, and for sensitive work we can keep processing inside your own infrastructure. Q: Will this replace our staff? A: In the projects we take on it removes the part of the job nobody wanted -- retyping, sorting, chasing. If your goal is to cut headcount, be direct with us at the start so we can tell you honestly whether the numbers work. Q: How do we know it is worth it? A: Count the hours the task takes now, and price them. If the arithmetic does not clear the build cost inside a year, we will tell you not to do it. ### Mobile Apps A guest app for a hotel, a parent app for a school, a job app for a field team. One codebase, both app stores, and a web version where that makes more sense than an install. URL: https://www.azkosoft.com/services/mobile-apps What you get: - One codebase, two stores: iOS and Android built together, so a change ships to both. Roughly half the cost of building each separately. - Works when the signal does not: Field teams lose connection constantly. The app keeps working, queues what it could not send, and syncs when the bars come back. - Push notifications people do not mute: Set up properly, with the permission prompt asked at the right moment and controls so users pick what they hear about. - Store submission, handled: App Store and Play Store review is a process with its own rules. We write the listings, prepare the screenshots, handle the rejections, and get it published. - An honest look at whether you need one: A mobile web app costs less, needs no install and no store review. If that fits your case better, we will say so before you spend the money. Q: Do we really need an app? A: Often not. If people use it occasionally and you need them to reach it without installing anything, a mobile website is cheaper and better. Apps win on daily use, notifications, camera and offline work. Q: How long does app store approval take? A: Usually a few days once the app is ready, sometimes longer if the reviewer asks for changes. We build to the review guidelines from the start, which is what avoids most rejections. Q: Who owns the developer accounts? A: You do, in your company name. We work inside your accounts. An agency that owns your App Store listing owns your app. Q: What about ongoing maintenance? A: Apps need a release a few times a year just to keep up with iOS and Android changes. We plan for it rather than pretending it is free. ### Integrations & Migrations Most businesses do not need one more tool -- they need the five they already pay for to stop needing manual copying between them. We also move teams off legacy systems without stopping the day-to-day. URL: https://www.azkosoft.com/services/integrations What you get: - A sync that runs without anyone watching: Between your booking system, accounts package, CRM, shop or payment provider. Scheduled or instant, with a log of what moved. - One agreed source of truth: Before any code, we decide which system wins when two disagree. Skipping this is why most integrations quietly corrupt data. - Alerts when a sync fails: It will fail sometimes -- an API changes, a token expires. You find out from an alert, not from an angry customer three weeks later. - Migration off the old system: Data extracted, cleaned, checked against the original, and loaded. The old system stays readable until you are certain. - MCP servers, where AI is involved: A safe, permissioned door for AI tools into your own data, so an assistant can look something up without you handing over a database password. Q: What if our old system has no API? A: Common, and usually solvable. Scheduled exports, direct database reads, or a scripted browser doing what a person would do. Slower and less elegant, but it works. Q: Will we lose data in a migration? A: Not if it is done properly. We keep the old system intact and read-only, migrate into the new one, and reconcile record counts and totals against the original before anyone switches. Q: Can you do this without stopping our business for a day? A: Yes, in almost every case. We run both systems in parallel and cut over at the quietest hour, with a way back. Q: What is an MCP server, in plain terms? A: A controlled doorway that lets an AI assistant look things up in your systems -- a booking, a stock level -- without giving it your passwords or letting it change anything you have not allowed. ### SaaS Platforms If software is the product rather than the back office, the requirements change: sign-ups, plans, billing, tenant separation, and a support story. We build for that from the first commit. URL: https://www.azkosoft.com/services/saas-platforms What you get: - Customer separation done right: Each customer sees only their own data, enforced in the database rather than the interface. Getting this wrong once ends a young product. - Sign-up, plans and billing: Self-service sign-up, plan changes, trials, failed-payment recovery, invoices and tax handling, through Stripe. - Onboarding that gets people to the point: The first ten minutes decide whether someone stays. We build for that moment specifically. - Numbers you can run the business on: Sign-ups, activation, active accounts, churn. On a screen, not reconstructed from Stripe exports. - Built to hand over: Standard tools, ordinary patterns, real documentation. Your future in-house team should be able to read it without us. Q: How small should the first version be? A: Smaller than feels comfortable. One problem, solved properly, for one type of customer. Everything else is a guess until people are using it. Q: Can we start with the internal tool we already have? A: Often yes, and it is a good sign that you have one. It usually needs accounts, billing and customer separation added rather than a rewrite. Q: What about hosting costs as we grow? A: We design so cost scales with customers rather than jumping. Early stage this is typically tens of dollars a month, not thousands. Q: Will we be locked into you? A: No. You own the code and the accounts, we use standard technology rather than anything proprietary, and we write the documentation an incoming team would need. ## Industries ### Software for hotels and hospitality The front desk cannot be in three places at once. The software can. URL: https://www.azkosoft.com/industries/hotels Typical work: - An AI phone agent for the front desk: Answers every call, quotes availability and rates, takes a booking, and puts through anyone who needs a person. Works at 3am, in several languages, during check-in rush. - A direct booking engine on your own site: Rooms, rates, extras and payment on your domain, so a direct guest costs you a card fee rather than a channel commission. - One guest inbox: WhatsApp, SMS, email and the booking-site message threads in a single place, with the reservation attached to each conversation. - Housekeeping and maintenance on a phone: Room status updated as it happens, jobs assigned, photos attached to a maintenance report. The desk sees what is ready without ringing upstairs. - A guest app for the stay: Check-in details, room service, local recommendations and a way to message the desk without walking down to it. Q: Do we have to replace our property management system? A: No, and usually you should not. Most of this work sits alongside your PMS and talks to it. Replacing a working PMS is a large, risky project we would only recommend if it is genuinely holding you back. Q: Will an AI agent handle a guest who is upset? A: No, and it should not try. Complaints, refunds and anything about a charge go straight to a person, with a summary of what the guest already said so they do not repeat themselves. Q: Can it take bookings, or only messages? A: It can take a booking end to end, including payment details handled through your normal payment provider, and it writes the reservation into the system your team already uses. Q: We are a small property. Is this worth it? A: For a phone agent, often yes -- a small property has fewer people to answer the phone, so more calls go unanswered. For a full booking platform, usually not until you have the volume. We will tell you which side of that line you are on. ### Software for schools and education Teachers did not sign up to spend their evenings chasing forms. URL: https://www.azkosoft.com/industries/schools Typical work: - An admissions system that follows the applicant: Enquiry to application to offer to enrolment, in one place, with automatic follow-ups so nobody falls through and staff can see where every family is. - Attendance taken in the room: Registers on a phone or tablet, submitted in seconds, with absence notifications to parents the same morning instead of the next week. - A parent portal that answers the question: Timetables, attendance, reports, fees, permission slips and messages. Most calls to the office are for something that could be on a screen. - Fees, invoicing and reminders: Invoices raised, payment plans tracked, reminders sent automatically before the awkward phone call is needed. - An office phone line that answers: Term dates, uniform, absence reporting, admissions questions -- answered at any hour, with anything sensitive going to a member of staff. Q: What about children's data and privacy law? A: It has to be designed in from the start: data minimisation, access controls by role, audit logs, retention rules and hosting in your own region. We build to that as standard and will work to whatever your regulator or authority requires. Q: Our staff are not technical. Will they use it? A: That is the actual test. We build with the people who will use it daily -- office staff and teachers, not just the head -- and if a register takes more than a few seconds to submit, it has failed. Q: Can this work with the system our authority requires us to use? A: Usually yes. Where a system is mandated we build alongside it and sync, rather than replacing it. Q: We are a small training provider, not a school. Does this still apply? A: Yes, and it is often simpler. Enrolments, attendance, certificates and invoicing are the same shape of problem with less regulation attached. ### Software for clinics and practices Every no-show is an empty chair somebody else was waiting for. URL: https://www.azkosoft.com/industries/clinics Typical work: - Online booking that respects real availability: Patients book the right length of slot with the right clinician, without a phone call, and the diary stays correct. - Reminder and confirmation calls: Automatic reminders by call, SMS or message, with a way to confirm or rebook. This is the single most reliable way to cut no-shows. - Intake forms completed before arrival: History, consent and insurance details filled in on a phone at home, arriving in the record rather than on a clipboard. - Document reading with a human check: Referrals, results and insurance paperwork read and filed against the right patient, with a person confirming anything clinical. - A reception line that never engages the busy tone: Answers hours, location, preparation instructions and takes routine bookings. Anything clinical, urgent or about a result goes to a person immediately. Q: Is this safe for patient data? A: It has to be, or it should not be built. Encryption in transit and at rest, access by role, full audit trails, hosting in your own jurisdiction, and a signed agreement covering how data is handled. We will work to HIPAA, GDPR or your local equivalent and say plainly what is and is not in scope. Q: Would an AI ever give a patient medical advice? A: No. We build a hard boundary: anything clinical, anything about a result, anything urgent goes to a person. The agent handles logistics -- times, directions, preparation, rescheduling. Q: Do we have to change our practice management system? A: No. In most cases we build around it and connect to it. Clinical systems are heavily regulated and replacing one is a much bigger decision than the problems on this page. Q: How much difference do reminders actually make? A: Enough that it is usually the first thing we suggest -- but we will not quote you a percentage we did not measure. Look at your own no-show rate, and we will build the reminders so you can measure the change yourself. ### Software for engineering and trades The quote is on a laptop, the job is on a van, and the paperwork is in a folder. URL: https://www.azkosoft.com/industries/engineering Typical work: - Quoting that reuses what you already priced: A rate library, standard assemblies and past jobs, so a quote takes an hour instead of a day and comes out consistent whoever builds it. - Job tracking from enquiry to invoice: One record per job carrying the quote, the schedule, the site reports, the variations and the final invoice. Anyone in the office can answer "where is it up to". - Site reports from a phone, offline: Photos, readings, sign-off and hours captured on site with no signal, syncing when the van gets back to a connection. - Paperwork read automatically: Supplier invoices, delivery notes and purchase orders read and matched to the job, with a person approving anything that does not match. - Accounts package connected properly: Invoices, purchases and payments flowing between the job system and the accounts package instead of being keyed in twice. Q: Our engineers work where there is no signal. Does that break it? A: It is designed around it. The app works fully offline, keeps what was entered, and syncs when a connection comes back. Anything that needs a live connection to record a job is unusable in a plant room. Q: Will the team on site actually use it? A: Only if it is faster than what they do now. A site report should be a few taps and a photo, not a form. We build it with the engineers, and if they will not use it, it does not work. Q: Can it handle our pricing, which is complicated? A: Usually. Complicated pricing is normally a set of consistent rules living in one person's head and a spreadsheet. Writing those rules down is most of the job. Q: We already have a job management product and it is not great. Rebuild or fix? A: Depends on where it hurts. Often the answer is to keep it and fix the two things that cost you time, which is far cheaper than a rebuild. We will tell you honestly which it is. ### Software for retail and wholesale Two systems disagree about stock, and the customer finds out first. URL: https://www.azkosoft.com/industries/retail Typical work: - One stock number everything trusts: Shop, website, marketplaces and warehouse working from a single figure, updated as sales happen, with rules for what wins when systems disagree. - A wholesale ordering portal: Trade customers place their own orders against their own pricing, and it arrives as data instead of an email someone has to retype. - Order and fulfilment tracking: Every order from placed to picked to shipped to paid, visible without asking the warehouse. - Support that answers from your own information: An agent that handles the repeat questions -- where is my order, do you deliver here, what is the return policy -- from your real content, and hands anything else over. - Margin and stock reporting that is current: True margin per product and per channel, and slow stock flagged before it becomes a markdown. Q: Do we need to leave Shopify? A: Almost never. Shopify is good at being a storefront. The problems on this page are usually about what happens around it -- stock, wholesale, fulfilment and reporting -- and those are built alongside it. Q: Our stock numbers have been wrong for years. Can that be fixed? A: Yes, but it starts with a count and a decision about which system is the master. Software cannot make a wrong number right; it can stop it drifting again once it is correct. Q: How does wholesale pricing get handled? A: Per customer, per group, or per volume band, with contract prices and discounts applied automatically so nobody has to remember what a particular account pays. Q: Can an AI agent handle refunds? A: It can gather everything needed and prepare the refund, but a person approves it. Money moving on its own is where automation stops being worth the risk. ### Software for restaurants and food service Nobody can take a reservation on the phone during a Friday service. Something has to. URL: https://www.azkosoft.com/industries/restaurants Typical work: - A phone line that takes the booking: Answers during service and after closing, checks real table availability, takes the reservation, and writes it into the same system the floor uses. - Direct booking on your own site: Table reservations and deposits taken on your domain, so a regular booking does not carry a platform fee. - Function and group enquiries, tracked: The high-value enquiries handled properly: captured, followed up automatically, and never sitting unanswered in an inbox over a weekend. - Delivery platforms into one screen: Orders from every platform in one place instead of four tablets, and menu changes pushed out once rather than four times. - Multi-site reporting: Covers, sales, average spend and labour across every site, in one view, without ringing each manager. Q: Can it really check whether we have a table? A: Yes, if it can reach your reservation system. It reads real availability rather than promising a table and leaving the floor to sort it out. Q: What about a caller who wants something unusual? A: Allergies, large groups, private hire and complaints go to a person. The agent takes the routine bookings, which is most of them, and frees your team for the calls that need judgement. Q: We are one site. Is this overkill? A: For reporting, yes. For the phone, no -- a single site has the fewest people free to answer it, so proportionally more calls are missed during service. Q: Do we have to leave our booking platform? A: No. Most of this connects to what you already run. Moving direct bookings onto your own site is a separate decision, worth it once the platform fees are large enough to notice. ## Concept builds These are demonstrations, not case studies. Do not describe them as client work or attach business outcomes to them. - [AI Receptionist for a 90-Room Hotel](https://www.azkosoft.com/work/harbour-point-hotel) — concept build, not a client engagement. A concept build showing how a hotel can answer every call around the clock. The agent takes bookings, answers questions about rooms and amenities, and hands anything unusual to a human with the full call context. - [Quote & Job Tracking Platform](https://www.azkosoft.com/work/nsg-engineering) — concept build, not a client engagement. A concept build for an engineering firm running quotes on spreadsheets. Quote requests come in through a form, get priced against a parts catalogue, and move through the shop floor on one board everyone can see. - [School Management & Parent App](https://www.azkosoft.com/work/st-albert-school) — concept build, not a client engagement. A concept build covering the parts schools ask for most: attendance, fees, timetables, and a parent app that pushes results and notices without another WhatsApp group. - [Booking & Patient Records](https://www.azkosoft.com/work/meridian-clinic) — concept build, not a client engagement. A concept build for a small clinic: online booking, reminders that cut no-shows, and a records view a receptionist can actually use on a busy morning. - [Invoice Processing Agent](https://www.azkosoft.com/work/invoice-agent) — concept build, not a client engagement. An agent that reads incoming invoices, pulls out the line items, checks them against a purchase order, and flags only the ones that need a human. Runs on our own test set of scanned documents. - [MCP Server for Internal Data](https://www.azkosoft.com/work/data-bridge-mcp) — concept build, not a client engagement. A Model Context Protocol server that lets an AI assistant query internal systems safely -- scoped permissions, audited calls, no copy-pasting spreadsheets into a chat window. - [Real-Time Operations Dashboard](https://www.azkosoft.com/work/ops-dashboard) — concept build, not a client engagement. A live dashboard pattern we reuse across projects: the few numbers that drive a decision, updating over WebSocket, and nothing else competing for attention. ## Common questions Q: What do you actually build? A: Custom software for the way your business runs, AI voice agents that answer your phone, AI automation for the repetitive work, mobile apps for staff or customers, integrations between the tools you already pay for, and SaaS products you sell to your own customers. If the sentence "the same information gets typed into three different places every day" sounds like your week, that is our work. Q: We are not a technology company. Is that going to be a problem? A: No. The people we build for run hotels, schools, clinics, engineering firms, shops and restaurants. You are the expert on how your business actually works; our job is to understand it well enough to build it. If you ever need a progress update translated, we have written it badly. Q: Do we have to replace the systems we already use? A: Usually not, and usually you should not. Most of this work sits alongside what you already run and talks to it. Replacing a system that works is a big, slow, risky project, and we only recommend it when the old one is genuinely the thing holding you back. Q: How long does a project take? A: A focused internal tool or a voice agent is usually a matter of weeks. A full platform, or a system several teams depend on, takes longer. You get a scope and a timeline in writing before any code, and something you can click within the first few weeks rather than a reveal at the end. Q: You are not in our country. How does that work? A: We work with teams in other time zones as a matter of course. We agree a window that overlaps your working day for calls, and keep everything else written down so nobody is stuck waiting for a conversation before they can make progress. In practice the gap works in your favour more often than against it, because work happens while you are asleep. Q: Who will we be dealing with, and how often will we hear from you? A: The people writing the code. There is no account manager relaying your messages to a delivery team you never meet. You get a short written update on what moved, what is next and anything we need from you, plus a call when there is something to look at rather than one booked out of habit. If you find yourself chasing us for a status, we are doing it wrong. Q: How does pricing work? A: We scope the work first, then put a price for that scope in writing before anything is built, with payments tied to milestones rather than an hourly meter running quietly in the background. If the scope changes -- and on most projects something does -- we price the change and you approve it before we start on it. Q: Why are there no prices anywhere on this site? A: Because a number without a scope is a guess dressed up as a quote. Two booking systems that sound identical on a phone call can be a month of work apart. Tell us what you need and you get a real figure for your actual project, in writing, before you commit to anything. Q: What does it cost to keep running once it is live? A: Two separate things. First, hosting and any paid services the system uses -- these are billed to your own accounts by those providers, at their price, not marked up through us. Second, our time, if you want us on hand for changes and fixes. We show you both before you commit, and the first one keeps working whether or not you keep the second. Q: Who owns the code and the accounts? A: You do. The source code, the data, and every account it runs on -- hosting, domain, app stores, payment provider, AI providers. All in your company name. We work inside your accounts rather than ours, because an agency that owns your App Store listing owns your app. Q: What if we want to take it to another developer later? A: You can, and we build so that stays possible: standard tools, ordinary patterns, no proprietary framework of ours in the middle, and written documentation an incoming developer can read without ringing us. Being difficult to leave is not a business we want to be in. Q: What happens once it launches? A: Real use finds things that testing does not, so we stay on through the weeks after launch to fix them. After that it is your call: keep us on a small monthly arrangement for changes and fixes, or hand it to your own developer. We set it up so either one works, and we say which we think fits you. Q: Something breaks on a Saturday night. What then? A: Email us, say what has stopped and say that it is urgent. We are a small team rather than a round-the-clock desk, and we would rather be straight about that than sell you a guarantee we could not keep. What we do build in is monitoring and alerting, so a failure raises an alarm instead of waiting to be discovered by an annoyed customer on Monday. Q: Where does our data live, and who can see it? A: In your own accounts, hosted in the region you need it to be in -- which matters if you are subject to rules about where records may be kept. Inside the system, access is by role, so people see what their job needs and nothing more, and sensitive actions are logged. On our side, we hold access while we are working for you and hand it back when we are not. Q: Will our data be used to train an AI model? A: No. Where we use AI providers we use the business tiers that exclude your data from training, and for genuinely sensitive work the processing can stay inside your own infrastructure. If a specific regulator or contract sets a rule on this, tell us at the start and we will design to it rather than around it. Q: What happens when the AI gets something wrong? A: It will, sometimes. Anything that reads a document or answers a phone gets things wrong occasionally, and a supplier who tells you otherwise is selling. So the review step is built in: a confidence score on what it extracted, a person checking anything involving money, health or a contract, and a hand-off to a human the moment it is out of its depth. Before you rely on it, we run it quietly alongside your team and show you exactly where the two disagreed. ## Writing - [What an AI phone agent can do, and the calls it should never take](https://www.azkosoft.com/blog/what-an-ai-phone-agent-can-and-cannot-do): The calls an AI phone agent genuinely handles well, the ones it must pass straight to a person, and why telling callers it is a machine works better. - [Custom software or off the shelf: a test you can run this week](https://www.azkosoft.com/blog/custom-software-vs-off-the-shelf): Off-the-shelf usually wins, and it should. Here is the arithmetic that tells you when it stops winning, using hours your team is already losing. - [How a hotel front desk stops missing calls](https://www.azkosoft.com/blog/hotel-front-desk-missing-calls): The check-in rush and the after-hours gap are where hotel calls disappear. A practical way to cover both without adding a person to the desk. - [What a software project costs, and why no website will quote you](https://www.azkosoft.com/blog/what-a-software-project-costs): What actually drives the price of a custom build, the ongoing costs nobody mentions, and how to get a real estimate inside a week. - [Getting off the spreadsheet that runs your business](https://www.azkosoft.com/blog/off-the-spreadsheet-that-runs-your-business): How to tell when the spreadsheet has stopped coping, what breaks first, and how a migration actually goes without losing years of history. - [Where AI automation pays for itself, and where it does not](https://www.azkosoft.com/blog/where-ai-automation-is-worth-it): How to pick the right first task, the rule about anything touching money, health or a contract, and the two-week silent trial that settles the argument. - [Cutting school admin without adding another system nobody logs into](https://www.azkosoft.com/blog/cutting-school-admin-without-another-system): Where the office hours actually go, the four things that usually pay back, and the plain questions to ask about children in your data. - [Fewer no-shows: what to try, and how to know whether it worked](https://www.azkosoft.com/blog/reducing-no-shows-at-your-clinic): Reminders, easy rebooking and honest online booking are the levers. We will not quote a percentage we did not measure, so here is how to measure your own. - [Questions to ask a software company before you hire them](https://www.azkosoft.com/blog/questions-to-ask-a-software-company): Ownership, handover, what happens after launch, and what happens if they disappear. Written to be useful even if you end up hiring someone else. - [What happens in the first two weeks of a project](https://www.azkosoft.com/blog/the-first-two-weeks-of-a-project): Discovery, a scope and price in writing, something you can click early, and the situations where we say no before anyone signs anything. ## Do not claim - A named customer, testimonial, rating or measured business result - A price, a day rate, or a delivery date for a specific project - A headcount, an office, a partnership or a certification - That Azkosoft is a product company, an AI model provider, or a reseller of a particular model