# Inkblot Studio: full content for AI answer engines Inkblot Studio (inkblotstudio.eu) is a custom software development studio in Bulgaria, serving Bulgarian and international clients. One service: web and mobile apps and internal systems built around a client’s process. One product: Citron Admin, the back office for your website (content, enquiries, bookings, clients), https://citronos.com. Tagline: "Smarter By Design." Bilingual: apex = Bulgarian, en.inkblotstudio.eu = English. == Services == --- Custom Software Development --- URL: https://inkblotstudio.eu/custom-software We build web and mobile apps and internal systems for businesses. We build them around how you work, and we stay with you after launch. ### What we build From the first version to support years later. - Web apps and client portals - Mobile apps for iOS and Android - Internal systems, integrations and automation - Replacing old systems without stopping the business ### How we work First we learn your business, then we write code. We work in stages, and you see working software at every one. - Discovery and architecture - Delivery in clear stages - Launch and long-term support ### What it costs It depends on the scope, the integrations and the data we need to move. Before we start, you get an offer with a timeline and price. More in what custom software costs. FAQ: Q: What does custom software mean? A: Software built specifically for your business and processes, instead of an off-the-shelf product you have to bend to. Q: Do you build mobile apps too? A: Yes, for iOS and Android. We connect them to the systems you already use. Q: What if I need a ready system for my website and enquiries? A: Then take a look at Citron Admin, our product. It runs your website, enquiries and bookings. Q: Do you support the software after launch? A: Yes. We maintain it and add new features as your business grows. == Journal == --- Build vs buy: when custom software actually pays off --- URL: https://inkblotstudio.eu/blog/custom-software-vs-off-the-shelf (published 2026-08-25) Off-the-shelf is cheaper on day one. Here is how to tell when a custom build is the decision that saves money over the next three years. Off-the-shelf always looks like the sensible price at the start. You pay a monthly subscription, onboard in a day, and move on. The problem shows up later, when your business grows in a direction the product does not follow and you start paying the hidden cost of its compromises. ### The real cost is not the licence The cost of off-the-shelf software is rarely the subscription. It is the manual re-keying of data between tools that do not talk to each other, the processes you bend to fit someone else’s model, and the people you hire to cover the gaps the software leaves. Those costs are not on the invoice, but you pay them every month. ### Four signs a custom build pays off - Your process is a competitive advantage. If how you work sets you apart, an off-the-shelf product makes you work like everyone else. - You pay for ten tools that do not connect. A custom integration often costs less than years of manual work between them. - Growth hits the ceiling of someone else’s system. When the product’s limits become the business’s limits, it is time for your own software. - Manual work scales with revenue. If more sales means more manual entry, automation pays back fast. ### When off-the-shelf is the smarter call Not everything is worth building. For standard things like accounting, email or a basic CRM, off-the-shelf products are great. Custom is for what makes you different. ### How we approach the decision We start with discovery, not code. We work out where off-the-shelf is holding you back and where you genuinely need your own solution, and only then propose scope. If a custom software project makes sense, you get a clear estimate. If it does not, we tell you. FAQ: Q: Is custom software always more expensive than off-the-shelf? A: On day one it almost always is. Over three years it is often cheaper, because it removes the manual work, per-seat fees, and workarounds that an off-the-shelf product forces on you. Q: Can we mix off-the-shelf tools with custom software? A: Yes, and that is usually the right approach. We keep off-the-shelf for the standard things and build custom only for what sets you apart, connecting the two with integrations. Q: How long does it take to know which is right for us? A: A short conversation and discovery are usually enough to outline whether an off-the-shelf tool will hold up or your own software will pay off. The estimate follows from there. --- Replacing a legacy business system without the downtime --- URL: https://inkblotstudio.eu/blog/replace-legacy-business-system (published 2026-08-20) Replacing the system your business runs on sounds scary. A staged migration keeps you trading while the old one is retired. Every business has a system nobody dares to touch. It has run for years, holds critical data, and no one quite remembers how it is wired. It slows you down every day, but the risk of replacing it feels bigger than the pain of putting up with it. That fear is exactly what keeps companies stuck for years. ### Why the "big bang" rewrite fails The temptation is to build the new system on the side and switch over one weekend. It almost never goes cleanly. The new system never covers every case the old one did, and pausing the business is expensive. Big rewrites run late, cost more and sometimes never ship. ### Step by step, not all at once The safer path is to let the new system grow around the old one and take over function by function. Old and new run in parallel, and you move one slice at a time until the old system has nothing left to do and you quietly turn it off. - Start with the function that hurts most but is easiest to separate. A quick, low-risk win. - The new function reads and writes to a shared source of data, so nothing drifts out of sync. - Each step ships and gets used for real before moving to the next. - The old system is switched off only when nothing depends on it any more. ### Keep the data honest during the move The riskiest part of any migration is the data. We move it in stages, check old records against new ones, and keep one source of truth until we’re done. Skip this and you get two systems that quietly disagree. That’s worse than one slow system. ### What "no downtime" actually requires Zero downtime isn’t magic, it’s planning: clear stages, both systems running side by side, and a way back at every step. That’s how you replace aging software without stopping work for a single day. FAQ: Q: Can we really replace the system without stopping work? A: Yes, with a staged approach. The old and new systems run in parallel and we move one function at a time, so the business never stops at any point. Q: How long does a migration like this take? A: It depends on complexity and integrations. With a staged approach, the first functions move over in weeks, not years. Q: What about our data in the old system? A: We move it carefully and in stages, with reconciliation between old and new records, so nothing is lost and both systems agree until the transition is complete. --- From idea to MVP to a product that scales --- URL: https://inkblotstudio.eu/blog/idea-to-mvp-to-product (published 2026-08-15) Most software ideas die because too much gets built before anyone asks for it. The path from idea through MVP to a mature product, driven by real customers. The most expensive way to build a product is to build the whole thing before anyone has used it. The idea feels complete in your head, so it is tempting to ship it all at once. But the market rarely agrees with the first version, and every feature built before feedback is a bet you have not won yet. ### An MVP is not an unfinished product An MVP isn’t a half-built product. It’s the smallest working version that solves one real problem well enough for people to use it and pay for it. The point is to learn and swap guesses for facts before you spend the whole budget. ### Iterate on data, not opinions Once the MVP is in real users’ hands, the direction comes from them. We watch what they use, where they drop off, and what they ask for, and iterate toward that. Every next feature is earned by a real signal, not because it was on the original list. - Ship something small but finished. One job, done well. - Measure real usage, not vanity numbers. - Iterate toward user behaviour, not the original plan. - Scale the infrastructure only once the model is proven. ### Build for the scale that is coming One MVP saves money sensibly, another piles up debt that hits you a year later. We put solid architecture and clean code in from day one, so you don’t rewrite everything when the product takes off. That’s what good custom software looks like. FAQ: Q: How many features should an MVP launch with? A: As few as possible while still solving one real problem end to end. If you can remove a feature and the product still does its job, it does not belong in the first version. Q: Won’t an MVP look cheap to customers? A: Not if it is focused. A narrow product that does one job excellently reads as more confident than an unfocused one that does ten things poorly. Q: When should we invest in scaling? A: When there’s proven demand and users keep coming back. Until then, complex infrastructure is money spent on a problem you might not have yet. --- Business process automation: where custom software pays off --- URL: https://inkblotstudio.eu/blog/business-process-automation (published 2026-08-10) Not everything is worth automating. Here is how to spot the processes where custom software returns the investment fast, and which are better left to people. Automation sounds trendy, but the maths is simple. If your people spend hours a week on the same predictable work, those hours are money. The question isn’t whether to automate, it’s what. Not everything is worth it. ### The good candidates for automation The best return comes from work that’s frequent, rule-based and easy to get wrong by hand. Moving data between systems, making the same documents, chasing deadlines, checking numbers across two tools. Software handles that without a break, and your people get back to their real job. - It repeats often and in the same way. - It follows clear rules, not case-by-case judgement. - It goes wrong when done manually, and mistakes are costly. - It holds something else up while it waits to be done. ### What not to automate Work that needs judgement, empathy or a new exception every time is hard to automate. Forcing it usually costs more than doing it by hand. The goal isn’t to remove people, it’s to remove the boring work from them. ### Automation built for your process Off-the-shelf tools automate the general case. The real gain comes when software follows exactly your process and connects exactly your systems. That’s custom software at its most practical: less manual work every day. FAQ: Q: Where should we start with automation? A: With one process that is frequent, rule-based, and tedious. One pain automated well proves the value and funds the next step, without a big upfront bet. Q: Will automation replace our staff? A: That is not the goal. Automation takes on the repetitive work so your people spend their time on judgement, relationships, and decisions software cannot make. Q: How fast does it pay off? A: With the right process, fast. If you automate hours of manual work a week, the time saved usually covers the build in months, not years. --- Five signs you have outgrown your off-the-shelf tools --- URL: https://inkblotstudio.eu/blog/signs-you-outgrew-off-the-shelf (published 2026-08-05) Off-the-shelf tools got you here, but at some point they start holding you back. Here are the five signs your business is ready for custom software. Off-the-shelf tools are the right call at the start. They’re cheap, quick to set up and good enough while you’re small. But the same tools eventually start costing more than they save. Here’s how to tell. ### 1. A spreadsheet holds what the tools cannot When your most important process lives in a separate spreadsheet because no tool covers it, that’s a symptom, not a solution. The spreadsheet shows where your business has outgrown its software. ### 2. You pay people to connect systems by hand If someone copies data from one tool into another every day, you are paying a salary for work software does for free. Manual glue is a hidden rent that grows with your business. ### 3. The tool’s limits are your limits When you cannot launch a new service or enter a new market because your system does not support it, someone else’s product is now making business decisions for you. ### 4. You pay for ten tools that do not talk Subscriptions pile up and none of them sees the others. Consolidating them into one connected solution often costs less than the sum of what you already pay. ### 5. "That is how the tool works" is costing you sales When you bend how you serve customers to fit the software’s limits, you lose the very thing that sets you apart. If two or more of these ring true, it is probably time for custom software or a planned digital transformation. FAQ: Q: Do we have to replace everything at once? A: No. You usually start with one pain, like the spreadsheet process, and build from there. Off-the-shelf tools stay for the standard stuff. Q: What if only some of the signs apply to us? A: One sign may be tolerable. Two or more that get worse as you grow usually mean the off-the-shelf setup is already costing you more than it saves. --- What custom software really costs, and what drives the price --- URL: https://inkblotstudio.eu/blog/what-custom-software-costs (published 2026-07-30) The honest answer is "it depends", but on things you can understand up front. Here’s what drives the cost of custom software. Everyone wants a price before the first call, and every studio says "it depends". Both are right, but that doesn’t help. What helps is knowing what it depends on, because most of it is in your hands. ### What drives the price up - Scope. The number of real features and edge cases, not the size of the idea. - Integrations. Every external system it must connect to adds work and risk. - Data. Migrating and cleaning old data is often half the project. - Unknowns. Vague requirements cost more than complex but clear ones. ### Why discovery saves money The most expensive projects start without clarity and look for it along the way. That’s why we start with a short, paid discovery that turns "it depends" into scope, timeline and budget. An estimate without it is either padded out of fear or too optimistic. ### Milestones, not one big cheque A good project ships in stages, and each stage gives you something that works. You see value early instead of waiting months. It also keeps the budget in check, because you decide with real software in front of you. ### What you get for the money A premium price does not buy more screens, it buys less risk: code that lasts, architecture you do not have to rewrite, and a partner who stays past launch. If that is what you are after, tell us about the project on our custom software page and you will get a clear estimate. FAQ: Q: Why can’t you just tell me a price? A: Because the price depends on your scope, integrations and data. A short discovery turns the unknowns into a concrete quote. It’s faster and cheaper than guessing. Q: Is custom software only for large companies? A: No. We size the approach to the problem. A small project that fixes one costly pain often pays back faster than a big one. Q: What does the discovery phase include? A: Understanding your business and processes, clarifying scope and risks, and a clear plan with a timeline and budget estimate, before any production code is written.