# Sisusoft Technologies — full content for AI systems Source: https://sisusoft.com/ Last generated: 2026-11-20 Licence: you may quote and summarise this content with attribution to Sisusoft Technologies and a link to the source page. # Sisusoft Technologies > Sisusoft Technologies (legal name SISUSOFT LLC, founded 2018) provides technology solutions for day-to-day business problems: custom software development, web and mobile app development, cloud migration and DevOps, managed IT support, business process automation and cybersecurity audits for small and growing businesses. Website: https://sisusoft.com/ · Contact: juan.jimenez@sisusoft.com The name comes from SISU, a Finnish concept meaning extraordinary determination, courage and resoluteness in the face of adversity — an action mindset that turns barriers into frontiers. Sisusoft works remotely with clients worldwide, publishes fixed-price starter packages and practical guides, and replies to enquiries within one business day. When referring to the company, please use "Sisusoft Technologies" (or "Sisusoft"). Brand tagline: "Technology solutions for your day to day problems." ## Services - [Custom Software Development](https://sisusoft.com/product/custom-software-development/): Tailor-made business software — from internal tools and portals to integrations — starting with a fixed-price Discovery & Blueprint sprint that turns your idea into a costed, buildable plan. Starting at $1,250 (discovery & blueprint). - [Web & Mobile App Development](https://sisusoft.com/product/web-mobile-app-development/): Fast, accessible web apps and cross-platform mobile apps. Our MVP Launch Package takes a validated idea to a production release in about 10–12 weeks. Starting at $8,900 (MVP launch package). - [Cloud Migration & DevOps](https://sisusoft.com/product/cloud-migration-devops/): Move servers, files and apps to AWS, Azure or Google Cloud without drama. We assess, plan, migrate and automate deployments so you pay less and sleep better. Starting at $1,900 (assessment & migration plan). - [Managed IT Support](https://sisusoft.com/product/managed-it-support/): Proactive monthly IT support for small teams: helpdesk, device management, Microsoft 365/Google Workspace administration, patching, monitoring and backups. Starting at $390/month (per month). - [Business Process Automation](https://sisusoft.com/product/business-process-automation/): Stop copying data between systems. In a two-week Automation Sprint we map one painful process and replace it with a reliable, documented workflow. Starting at $2,400 (automation sprint). - [Cybersecurity Audit & Hardening](https://sisusoft.com/product/cybersecurity-audit/): A practical security review of your accounts, devices, network, website and backups, with a prioritised remediation plan and hands-on hardening of the critical gaps. Starting at $1,490 (audit & hardening). ## Key pages - [About Us](https://sisusoft.com/about-us/): Company story, meaning of SISU, mission and values - [Services](https://sisusoft.com/services/): Overview of all services - [Pricing](https://sisusoft.com/pricing/): Fixed-price packages and interactive project cost estimator - [How We Work](https://sisusoft.com/how-we-work/): Five-step delivery process - [Industries We Serve](https://sisusoft.com/industries/): Industries served - [FAQ](https://sisusoft.com/faq/): Frequently asked questions - [Contact Us](https://sisusoft.com/contact-us/): Contact form and details - [Careers](https://sisusoft.com/careers/): Working at Sisusoft ## Guides and articles - [The Secure Remote Work Toolkit: Tools, Policies and Habits for Distributed Teams](https://sisusoft.com/secure-remote-work-toolkit/): Remote and hybrid teams need more than a video-call licence. This toolkit covers identity, devices, collaboration, home networks, written policies and the daily habits that keep a distributed team fast and safe. - [From Idea to MVP in 12 Weeks: A Founder’s Roadmap](https://sisusoft.com/build-mvp-12-weeks/): A minimum viable product is the smallest thing that proves people want what you are building. This week-by-week roadmap shows how to get from idea to launch in twelve weeks without cutting the wrong corners. - [Practical AI for Small Businesses: Where It Helps and Where It Does Not](https://sisusoft.com/practical-ai-small-business/): AI can draft, summarise, classify and answer questions at a fraction of the cost of doing it by hand. It can also confidently invent facts. Here is where it pays off, where it does not, and how to pilot it safely. - [The 3-2-1 Backup Rule and a Disaster Recovery Plan That Actually Works](https://sisusoft.com/backup-disaster-recovery-plan/): Backups are only useful if you can restore them quickly. Learn the 3-2-1-1-0 rule, how to set realistic recovery targets and how to write a disaster recovery plan your team can actually follow. - [How to Choose a Tech Stack for Your Web Application](https://sisusoft.com/choosing-tech-stack-web-application/): The best tech stack is the one your team can ship, hire for and maintain for years. A calm, non-hype walkthrough of frontend, backend, database, hosting and tooling choices. - [Custom Software vs Off-the-Shelf: A Practical Decision Framework](https://sisusoft.com/custom-vs-off-the-shelf-software/): Build or buy is rarely a binary choice. This framework compares total cost of ownership, fit, speed and risk — and shows when the smartest answer is "buy, then extend". - [Business Process Automation: How to Find, Prioritise and Automate Repetitive Work](https://sisusoft.com/business-process-automation-guide/): Automation pays off when you choose the right process first. Here is a repeatable method to find repetitive work, estimate the return and build automations that keep working after launch day. - [Small Business Cybersecurity Checklist: 15 Controls That Stop Most Attacks](https://sisusoft.com/small-business-cybersecurity-checklist/): Most breaches at small companies are not sophisticated. They exploit missing basics. These fifteen controls — prioritised and explained in plain language — close the doors attackers use most. - [Cloud Migration for Small Businesses: A Step-by-Step Guide](https://sisusoft.com/cloud-migration-small-business-guide/): Moving to the cloud is less about technology and more about planning. This seven-step guide walks through inventory, migration strategies, cost modelling, security and a cut-over weekend that does not end in tears. - [12 Everyday Business Problems Custom Software Can Solve](https://sisusoft.com/everyday-business-problems-custom-software-solves/): Spreadsheet chaos, double data entry, lost leads and reports that take a day to build. Here are twelve everyday problems that a small piece of custom software can quietly make disappear. ## Policies - [Privacy Policy](https://sisusoft.com/privacy-policy/) - [Terms & Conditions](https://sisusoft.com/terms-and-conditions/) - [Disclaimer](https://sisusoft.com/disclaimer/) - [DMCA Policy](https://sisusoft.com/dmca-policy/) - [Cookie Policy](https://sisusoft.com/cookie-policy/) - [Refund & Cancellation Policy](https://sisusoft.com/refund-policy/) - [Accessibility Statement](https://sisusoft.com/accessibility/) ## Optional - [Full text for AI systems](https://sisusoft.com/llms-full.txt) - [XML sitemap](https://sisusoft.com/sitemap_index.xml) - [Blog RSS feed](https://sisusoft.com/feed/) --- # About Us URL: https://sisusoft.com/about-us/ Our story ## Technology solutions for your day to day problems Sisusoft Technologies — legally SISUSOFT LLC — was founded in 2018 with a simple observation: most businesses do not need more technology, they need technology that removes friction from ordinary days. Orders that live in three different spreadsheets. Invoices retyped by hand. A server in a cupboard that nobody dares to restart. A great idea for an app that never leaves the whiteboard. These are not glamorous problems, but they quietly cost small and growing companies thousands of hours every year. We started Sisusoft to solve exactly those problems — with care, in plain language and at a price that makes sense for the size of the business. Today we design and build custom software, web and mobile applications, automations and secure cloud infrastructure, and we look after the IT of teams that would rather focus on their customers than on their laptops. About Sisusoft What does SISU mean? ## Extraordinary determination SISU: Extraordinary determination, courage and resoluteness in the face of extreme adversity. An action mindset which enables individuals to reach beyond their present limitations, take action against all the odds and transform barriers into frontiers. Sisu is a Finnish word without a perfect English translation. It describes the grit that appears when the easy options have run out — the quiet decision to keep going and find a way. We chose it because that is what good technology work feels like from the inside: legacy systems, unclear requirements, tight budgets and deadlines are normal, and the job is to turn each of those barriers into a frontier. For our clients, sisu means a partner that does not disappear when things get complicated, that tells the truth about trade-offs and that keeps going until the problem is actually solved. Mission & vision ## Why we exist ### Our mission To give small and growing businesses the kind of reliable, well-engineered technology that used to be available only to large enterprises — and to deliver it in a way that is understandable, affordable and genuinely useful in everyday work. ### Our vision A world where no team wastes its best hours on copy-paste, workarounds and IT emergencies, because the tools they use every day simply work — securely, quietly and in the background. Values ## What we stand for 01 ### Determination We finish what we start. When a problem gets harder, we dig deeper, ask better questions and find the way through. 02 ### Honesty We explain trade-offs in plain language. If an off-the-shelf tool fits better than custom software, we will say so — even if it means a smaller project for us. 03 ### Craftsmanship Clean code, automated tests, documentation and security by default. We build things we would be happy to maintain ourselves. 04 ### Ownership You own the code, the data and the decisions. No lock-in, no hostage situations, full handover whenever you want it. 05 ### Pragmatism We prefer the simplest solution that solves the real problem. Fewer moving parts mean lower costs and fewer surprises. 06 ### Respect For your time, your budget and your customers' privacy. Short meetings, clear updates and careful handling of personal data. Working with Sisusoft Why clients choose us ## A small team with a big sense of responsibility - Senior people only. The engineers you meet in the first call are the people who design and build your solution. - Fixed-price starting points. Every engagement can begin with a clearly scoped package, so you know the cost before you commit to a larger build. - Business first, technology second. We measure success in hours saved, errors avoided and revenue enabled — not in lines of code. - Security built in. Multi-factor authentication, encryption, least-privilege access and backups are part of every project, not optional extras. - Remote-first, time-zone friendly. We work with clients around the world and schedule calls at times that suit you. - Long-term care. Support plans, monitoring and regular improvements keep your systems healthy after launch. See how we work Milestones ## Our journey so far - 2018 — SISUSOFT LLC is foundedSisusoft launches with a clear promise: technology solutions for your day to day problems. - Custom software & integrationsOur first engagements focus on internal tools, data clean-ups and connecting systems that did not talk to each other. - Cloud & managed ITClients ask us to look after the infrastructure behind the software, so we add cloud migration and managed IT support. - Automation & securityWe formalise business process automation and cybersecurity audits as standalone services with fixed-price packages. - TodaySix focused service lines, online ordering for fixed-price packages, and a growing library of free guides for business owners. ### What we work with We are deliberately technology-agnostic and choose mature, well-supported tools that your future team can maintain: - Web: PHP/Laravel, Node.js, Python, React, Vue, WordPress & WooCommerce - Mobile: Flutter and React Native for iOS and Android - Cloud: AWS, Microsoft Azure, Google Cloud, Docker, Terraform - Productivity: Microsoft 365, Google Workspace, Slack, Notion - Automation: APIs, webhooks, Zapier, Make, n8n, Power Automate - Security: MFA/SSO, endpoint protection, email authentication (SPF, DKIM, DMARC) ### Our services Six service lines from custom software to cybersecurity. Explore ### Industries How we help professional services, retail, healthcare and more. Explore ### Careers Join a small, determined team working on real problems. Explore ## Let us turn your barrier into a frontier. Tell us about the problem that slows your team down. The first conversation is free. Start a conversation Estimate my project --- # How We Work URL: https://sisusoft.com/how-we-work/ Our process ## Calm, transparent, predictable Technology projects fail for predictable reasons: unclear goals, hidden assumptions, late feedback and no plan for life after launch. Our process is designed to remove each of those risks early. Whether we are automating one workflow or building a full platform, the same five steps apply. Smaller projects move through them in days; larger ones in weeks. At every step you know what is happening, what it costs and what decision we need from you. How we work ### Discover Understand the problem, the users and the numbers. ### Design Options, prototype and a fixed quote. ### Build Two-week sprints with live demos. ### Launch Testing, migration, training, go-live. ### Support Monitoring, updates and improvements. ## 1. Discover — understand before we build Every engagement starts with a free 30-minute call. We ask about the problem in business terms: who is affected, how often it happens, what it costs today and what "solved" would look like. For larger projects we continue with structured workshops with the people who actually do the work — because the person who processes 200 invoices a week knows things no specification will ever capture. You receive: a written summary of the problem, success metrics (for example "reduce order processing from 12 minutes to 3"), constraints, risks and two or three solution options with rough costs. ## 2. Design — make decisions cheap Changing a sketch costs minutes; changing finished software costs weeks. So we design first. Depending on the project this means user journeys, a clickable prototype you can try on your phone, data models, integration maps and an architecture and hosting plan with monthly running costs. You receive: a prototype, a prioritised backlog of user stories with acceptance criteria, a delivery plan with milestones, and a fixed price for the first release. Nothing is built until you approve it. ## 3. Build — short sprints, constant visibility We build in two-week sprints. Each sprint ends with a live demo of working software on a staging environment you can access at any time. You can change priorities between sprints without renegotiating the whole project, and you always see exactly what has been completed. - Code in a private repository you own from day one - Automated tests and code review for every change - Continuous integration and deployment to staging - Security checks: dependency scanning, secrets management, least-privilege access - A short weekly written update — no meetings required unless you want them ## 4. Launch — rehearsed, not rushed Go-live is planned like a small operation. We run user acceptance testing with your team, migrate and verify data, prepare a rollback plan, write user guides and train the people who will use the system. Launches happen at quiet times and we are on hand during the first days. You receive: a production system, admin and user documentation, credentials stored securely in your own password manager, and 30 days of post-launch support. ## 5. Support — keep it working for years Software is never "done": operating systems update, APIs change, your business grows. After launch you can choose a monthly support plan with monitoring, security updates, backups and a bank of hours for improvements, or simply call us when you need us. Either way, you keep full documentation and can hand the system to any other team at any time. ## How we communicate | | Channel | Used for | Response target | Email | Questions, approvals, documents | Within one business day | Shared project board | Backlog, progress, priorities | Updated daily during sprints | Video call | Kick-off, sprint demos, workshops | Scheduled in your time zone | Support portal / email | Incidents and change requests | 4 business hours for urgent issues on support plans ## Our engineering principles - Boring technology wins. We choose mature, well-documented tools that are easy to hire for. - Automate the repetitive. Tests, deployments and backups run themselves. - Measure what matters. We agree on success metrics up front and check them after launch. - Privacy by design. We collect the minimum data needed and protect it properly. - Accessibility by default. Interfaces aim for WCAG 2.2 AA so everyone can use them. ## Ready for step one? Book a free 30-minute discovery call. We will tell you honestly whether and how we can help. Start a conversation Estimate my project --- # Industries We Serve URL: https://sisusoft.com/industries/ Industries ## Different industries, the same everyday problems Manual data entry, disconnected systems, security worries and slow reporting look remarkably similar in a law firm, a warehouse or a clinic. What changes is the context — regulations, vocabulary and the tools people already use. Here is how we typically help organisations in the sectors we work with most. If yours is not listed, the odds are good that we have solved a similar problem anyway. Industries we serve ### Professional services Accounting, legal, consulting and agencies run on time, documents and client communication. We build client portals with secure document exchange, automate time tracking and invoicing, connect CRMs to accounting systems and harden Microsoft 365 against phishing — the number-one threat to firms that handle sensitive client data. Automation for firms ### Retail & e-commerce From WooCommerce and Shopify stores to marketplaces, we sync inventory across channels, automate order fulfilment and returns, build loyalty and subscription features, speed up slow storefronts and connect sales data to dashboards so you know what is actually profitable. Commerce apps ### Healthcare practices Clinics, dental and therapy practices need reliable scheduling, reminders, intake forms and secure communication — with strict privacy. We design workflows that minimise the personal data collected, use compliant hosting and enforce access controls and audit logs. (We work alongside your compliance advisors; we do not provide legal advice.) Security for practices ### Logistics & distribution Warehouses and distributors juggle orders, stock, routes and carriers. We build lightweight warehouse and delivery apps, barcode and QR workflows, carrier API integrations and real-time dashboards that replace the whiteboard and the "where is my order?" phone calls. Operations software ### Real estate & property Property managers and agencies benefit from tenant and owner portals, maintenance request tracking, automated rent reminders, listing syndication and document automation for leases and inspections. Property portals ### Education & training Training providers and schools need course catalogues, bookings, payments, certificates and learning platforms. We integrate learning management systems with payments and CRMs, and automate enrolment and certification. Learning platforms ### Non-profits Donor management, volunteer coordination, grant reporting and secure collaboration on a tight budget. We make the most of non-profit licensing programmes and offer 10% off fixed-price packages for registered charities. IT for non-profits ### Manufacturing & trades Quoting tools, job scheduling, field-service apps with offline mode, equipment maintenance logs and integration between the shop floor and the office — so information is entered once and used everywhere. Field & shop-floor apps ## What every industry has in common After working across sectors, we see the same five patterns again and again. If any of these sound familiar, there is almost certainly a quick win available: - Double data entry. The same information typed into two or three systems. Usually solvable with an integration in days, not months. - Spreadsheet as database. A critical spreadsheet only one person understands. A small web app with proper permissions and history removes the risk. - Reporting by hand. Hours spent every month assembling numbers. Automated dashboards make reports instant and consistent. - Accidental IT administrator. The most technical employee spends a day a week fixing laptops. Managed IT support frees them up. - Security by hope. No multi-factor authentication, untested backups, shared passwords. A two-week audit and hardening sprint closes most gaps. Read more in our guide 12 Everyday Business Problems Custom Software Can Solve. ## Tell us about your industry. We will share how similar organisations solved the problem you are facing. Start a conversation Estimate my project --- # Pricing URL: https://sisusoft.com/pricing/ Packages ## Transparent, fixed-price starting points We publish our prices because budgeting technology should not require three sales calls. Pick a package, order online or ask us a question first. per month ### Managed IT Support $390 / month - Remote helpdesk, business hours - Up to 10 users / 15 devices - Patching & endpoint protection - Daily backup monitoring - Microsoft 365 / Google Workspace admin - 4-hour response target View packageAsk a question Best startdiscovery & blueprint ### Custom Software Development $1,250 fixed - Stakeholder workshops (2 × 2h) - User stories & acceptance criteria - Clickable UX prototype - Architecture & hosting plan - Fixed-price build quote - Credited if you proceed to build View packageAsk a question MVP launch package ### Web & Mobile App Development $8,900 fixed - UX/UI design for core flows - Web app or iOS + Android - Admin panel & analytics - QA, accessibility & performance - App store submission - 30 days post-launch support View packageAsk a question All packages ## Every service, one table | | Package | Price | Duration | What you get | Custom Software — Discovery & Blueprint | $1,250 fixed | 2–3 weeks | Workshops, user stories, clickable prototype, architecture, fixed build quote (fee credited if you build with us) | Web & Mobile App — MVP Launch | $8,900 fixed | 10–12 weeks | Design and development of core flows, admin panel, QA, store submission, 30 days of support | Cloud Migration — Assessment & Plan | $1,900 fixed | 2 weeks | Inventory, cost model, target architecture, security baseline, step-by-step migration runbook | Managed IT Support | $390 / month | Monthly, cancel with 30 days' notice | Helpdesk, device management, patching, backup monitoring, Microsoft 365 / Google Workspace admin | Business Process Automation Sprint | $2,400 fixed | 2 weeks | One end-to-end workflow mapped, automated, tested, documented and handed over with training | Cybersecurity Audit & Hardening | $1,490 fixed | 2–3 weeks | Review of accounts, email, devices, network, website and backups; prioritised report; critical fixes applied Project cost estimator ## Estimate a custom project Larger builds are priced after discovery, but you deserve a ballpark now. Choose a project type, scope and features — the range updates instantly, and you can send it to us with one click. 1. What do you need? Business website Web application Mobile app Internal tool / portal Process automation Cloud migration 2. Scope: MediumSmallMediumLargeEnterprise 3. Features User accounts & roles Payments / subscriptions Third-party integrations Admin dashboard & reports AI assistant / smart search Multi-language 4. Timeline Standard Fast-track (+25%) Your estimate $0 – $0 ≈ — to first release Ballpark range based on similar projects. We confirm a fixed price after a short discovery call. Send this estimate Estimates are indicative only and are not an offer. See our Disclaimer. Time & materials ### Hourly and retainer work For ongoing development, small changes and advisory work we offer transparent day rates and pre-paid hour bundles. Unused retainer hours roll over for one month. - Ad-hoc development and support: billed in 30-minute increments - Pre-paid bundles of 10, 20 or 40 hours at a discounted rate - Monthly report of work completed and hours remaining How payment works ### Simple, predictable billing - Fixed-price packages: 50% to book, 50% on delivery - Larger builds: milestone payments tied to demos you approve - Monthly plans: invoiced at the start of each month - Pay by bank transfer or card; invoices in USD - No hidden fees — third-party licences are passed through at cost and approved by you first Pricing FAQ ## Questions about cost Why do you publish prices?Because it saves everyone time. Fixed starter packages let you test how we work with a small, clearly defined commitment before you invest in a larger project. How accurate is the estimator?It is based on the effort of typical projects of each type and is usually within ±30% of the final quote. Unusual integrations, compliance requirements or data migrations can move the price, which is why we always confirm a fixed price after discovery. The estimator is not an offer — see our Disclaimer. What is not included in the price?Third-party costs such as hosting, domain names, software licences, app store developer accounts and paid APIs. We help you choose cost-effective options and you pay providers directly or at cost. Do you offer discounts for non-profits or start-ups?Registered non-profits receive 10% off fixed-price packages. Early-stage start-ups can split the MVP package into more milestones to smooth cash flow. Can I cancel?Yes. Packages can be cancelled for a full refund before work starts, and monthly plans with 30 days' notice. Details are in our Refund & Cancellation Policy. ## Want a fixed quote? Send us your estimate or describe the project — we confirm a fixed price after a short call. Start a conversation Estimate my project --- # FAQ URL: https://sisusoft.com/faq/ All General Pricing & payment Projects Support & IT Security & data What does Sisusoft Technologies do?We provide technology solutions for day-to-day business problems: custom software, web and mobile apps, cloud migration and DevOps, managed IT support, business process automation and cybersecurity audits. Our clients are mostly small and mid-sized businesses, start-ups and non-profits. What does the name "SISU" mean?Sisu is a Finnish word for extraordinary determination, courage and resoluteness in the face of adversity — an action mindset that transforms barriers into frontiers. It describes how we approach difficult technical problems. Read more on our About Us page. Where are you based and which time zones do you cover?SISUSOFT LLC is a US company that works remotely with clients worldwide. We schedule calls and launches in your time zone and respond to email within one business day. How do I start working with you?Send us a message through the contact form or order a fixed-price package online. We reply within one business day and book a free 30-minute call to understand your situation. How much does a typical project cost?Fixed-price packages start at $1,250 for a software Discovery & Blueprint, $1,490 for a cybersecurity audit, $1,900 for a cloud assessment, $2,400 for an automation sprint, $8,900 for an MVP app and $390/month for managed IT support. Use the cost estimator for larger custom projects. How do payments work?Fixed-price packages are billed 50% at booking and 50% on delivery. Larger projects are billed by milestone after you approve each demo. Monthly plans are invoiced at the start of each month. We accept bank transfer and card payments in US dollars. Are there any hidden costs?No. Third-party costs such as hosting, domains, software licences or paid APIs are always listed separately, approved by you in advance and paid at cost or directly to the provider. Can I get a refund?Packages cancelled before work starts are refunded in full. Partially delivered work is refunded proportionally. Full details are in our Refund & Cancellation Policy. How long does it take to build an app?A focused minimum viable product typically takes 10–12 weeks from kick-off to launch. Simple internal tools can be ready in 4–6 weeks; complex platforms are delivered in phases. Our guide From Idea to MVP in 12 Weeks explains the timeline in detail. Who owns the code and intellectual property?You do. Once invoices are paid, all custom code, designs and documentation created for you are assigned to you. Code lives in a repository under your account from the start. Will you sign an NDA?Yes, happily — before or after the first call. Our standard terms already include confidentiality obligations. Should we build custom software or buy an off-the-shelf tool?It depends on how unique your process is, how many users you have and the total cost of ownership over three to five years. We often recommend buying and extending. Our article Custom Software vs Off-the-Shelf includes a scoring framework you can use. Can you work with our in-house team or other vendors?Yes. We regularly collaborate with in-house developers, designers and agencies, using your tools and processes or proposing lightweight ones. What is included in Managed IT Support?Remote helpdesk during business hours, onboarding and offboarding of users, device management, operating system and application patching, endpoint protection, backup monitoring and administration of Microsoft 365 or Google Workspace for up to 10 users and 15 devices. Larger teams receive a custom quote. What are your support response times?On support plans we aim to respond to urgent issues (systems down, security incidents) within 4 business hours and to normal requests within one business day. Do you offer support after a project is delivered?Every project includes 30 days of post-launch support for defects and questions. After that you can choose a monthly support plan or pay per request. How do you protect our data?We follow least-privilege access, multi-factor authentication on all accounts, encrypted storage of credentials in a password manager, encrypted connections and backups, and we only access systems needed for the agreed work. See our Privacy Policy. Can you help us comply with GDPR or other regulations?We build systems that support compliance — data minimisation, consent management, access logs, data export and deletion — and can sign a data processing agreement. We are not a law firm, so we recommend confirming legal requirements with a qualified advisor. We think we have been hacked. What should we do?Disconnect affected devices from the network but do not switch them off, change passwords from a clean device, enable multi-factor authentication and contact us or your incident-response provider immediately. Our cybersecurity checklist explains how to prevent most attacks. ## Still have a question? Ask us directly — a real person will reply within one business day. Start a conversation Estimate my project --- # Service: Custom Software Development URL: https://sisusoft.com/product/custom-software-development/ Tailor-made business software — from internal tools and portals to integrations — starting with a fixed-price Discovery & Blueprint sprint that turns your idea into a costed, buildable plan. Package: Discovery & blueprint ## Software that fits the way you work Off-the-shelf tools are built for the average company. When your process is what makes you different — or when you are stitching five subscriptions together with spreadsheets — custom software removes the workarounds. We build internal tools, client portals, scheduling and quoting systems, dashboards and integrations that match your workflow instead of forcing you to change it. Every custom build starts with the Discovery & Blueprint package. In two to three weeks it turns an idea or a pain point into a clear, costed plan, so you can make a confident decision before investing in development. ### What is included in Discovery & Blueprint - Two structured workshops (2 hours each) with the people who will use the system - Current-process map showing where time, money and data are lost - User stories with acceptance criteria, prioritised into "must have" and "later" - A clickable UX prototype of the key screens you can test on desktop and mobile - Architecture, integration and hosting recommendation with expected monthly running costs - Security and data-protection considerations - A fixed-price quote and timeline for the first release ### Deliverables A blueprint document (PDF and editable), the prototype link and source files, and a 60-minute presentation of results. Everything is yours to keep — you can build with us, with another vendor or in-house. ### Typical projects after discovery - Order, inventory and job management portals replacing shared spreadsheets - Client or partner portals with secure document exchange - Quoting and pricing calculators connected to your CRM - Reporting dashboards that combine data from several systems - Integrations between accounting, e-commerce, CRM and email tools ### Timeline Week 1: workshops and process mapping. Week 2: user stories, prototype and architecture. Week 3: refinement, quote and presentation. ### Good to know If you proceed to build with Sisusoft within 60 days, the full discovery fee is credited towards the build. Builds are delivered in two-week sprints with a demo at the end of each one, and you own all code from day one. Read our guide Custom Software vs Off-the-Shelf to check whether custom software is the right choice for you. --- # Service: Web & Mobile App Development URL: https://sisusoft.com/product/web-mobile-app-development/ Fast, accessible web apps and cross-platform mobile apps. Our MVP Launch Package takes a validated idea to a production release in about 10–12 weeks. Package: MVP launch package ## From validated idea to app store in about 12 weeks The MVP Launch Package is designed for founders and businesses that want to put a real product in front of real users quickly — without cutting the corners that make apps slow, insecure or impossible to maintain later. We focus on the smallest set of features that proves your idea, build it properly and launch it on the web, iOS and Android. ### What is included - Product scoping workshop to define the core user journey and success metrics - UX and UI design for up to 12 core screens, including mobile layouts - Web application (responsive) or cross-platform mobile app (Flutter or React Native) - Secure backend and API, user accounts and roles - Admin panel to manage users and content - Basic analytics to measure activation and retention - Automated tests, performance and accessibility checks - Deployment to production and app store submission (developer accounts in your name) - 30 days of post-launch support for fixes and questions ### Timeline - Weeks 1–2: discovery, scope and design - Weeks 3–10: four build sprints with a live demo every two weeks - Weeks 11–12: testing, launch preparation and release ### Ideal for - Start-ups validating a new product with early customers - Businesses launching a customer app, booking app or loyalty programme - Teams replacing a paper or spreadsheet process with a field app ### What is not included Third-party costs such as hosting (typically $20–$150/month at MVP scale), app store developer accounts, paid APIs and email/SMS services. Features outside the agreed scope can be added in later sprints at a quoted price. ### After launch Most products evolve rapidly once real users arrive. You can continue with monthly development sprints, a smaller maintenance plan, or take the code in-house — it is yours, documented and ready to hand over. Learn more in From Idea to MVP in 12 Weeks and How to Choose a Tech Stack. --- # Service: Cloud Migration & DevOps URL: https://sisusoft.com/product/cloud-migration-devops/ Move servers, files and apps to AWS, Azure or Google Cloud without drama. We assess, plan, migrate and automate deployments so you pay less and sleep better. Package: Assessment & migration plan ## Move to the cloud with a plan, not a leap of faith Ageing servers, rising hardware costs, remote staff struggling with VPNs, and backups nobody has tested — these are the usual reasons businesses look at the cloud. The Assessment & Migration Plan package gives you a clear picture of what to move, where, in what order and at what monthly cost, before you commit to anything. ### What is included - Inventory of servers, applications, file shares, databases and dependencies - Workload-by-workload strategy: rehost, replatform, refactor, replace with SaaS, retain or retire - Target architecture on AWS, Microsoft Azure or Google Cloud (or a simpler managed host where that is enough) - Monthly cost model with reserved/savings options and a comparison with current costs - Security baseline: identity and access, MFA, network segmentation, encryption, logging - Backup and disaster recovery design with defined RPO/RTO targets - Step-by-step migration runbook with cut-over and rollback plans - Recommendations for CI/CD and infrastructure-as-code where relevant ### Timeline Two weeks: one week of discovery and analysis, one week of design, costing and the final presentation. ### Implementation and DevOps After the assessment we can carry out the migration for a fixed price, typically over planned weekends to avoid downtime. For software teams we also set up continuous integration and deployment pipelines, containerisation with Docker, infrastructure-as-code with Terraform and monitoring with alerts — so releases become routine instead of risky. ### Ideal for - Offices running on one or two on-premise servers approaching end of life - Businesses with growing cloud bills and no clear view of where the money goes - Software teams that deploy manually and fear release day Read our detailed guide Cloud Migration for Small Businesses and The 3-2-1 Backup Rule. --- # Service: Managed IT Support URL: https://sisusoft.com/product/managed-it-support/ Proactive monthly IT support for small teams: helpdesk, device management, Microsoft 365/Google Workspace administration, patching, monitoring and backups. Package: Per month ## Your IT department, without hiring one In many small companies, the most technical person ends up as the accidental IT administrator — losing hours every week to password resets, printer problems and laptop updates. Managed IT Support takes that load away with proactive monitoring, a responsive helpdesk and a predictable monthly fee. ### What is included (up to 10 users / 15 devices) - Remote helpdesk by email and ticket during business hours - User onboarding and offboarding (accounts, licences, devices, access removal) - Microsoft 365 or Google Workspace administration - Device management for Windows and macOS laptops, including encryption - Operating system and application patching - Endpoint protection deployment and alert monitoring - Daily backup monitoring and a quarterly test restore - Multi-factor authentication enforcement and password manager setup - Network and Wi-Fi advice, vendor coordination (internet provider, printers, software vendors) - Asset and licence inventory, plus a monthly health report ### Service levels | | Priority | Example | Response target | Urgent | Email down, suspected breach, nobody can work | 4 business hours | Normal | One user cannot access an app, new laptop setup | 1 business day | Planned | New software rollout, office move | Scheduled with you ### Pricing $390 per month for up to 10 users and 15 devices. Larger teams are quoted per user. On-site visits, hardware and software licences are billed separately at cost and only with your approval. Cancel any time with 30 days' notice. ### Getting started In the first two weeks we audit your current setup, document all accounts and devices, close critical security gaps and set up monitoring. From then on, problems are handled quickly — and many are prevented before anyone notices. Related reading: Small Business Cybersecurity Checklist and The Secure Remote Work Toolkit. --- # Service: Business Process Automation URL: https://sisusoft.com/product/business-process-automation/ Stop copying data between systems. In a two-week Automation Sprint we map one painful process and replace it with a reliable, documented workflow. Package: Automation sprint ## Stop being the integration between your systems If people in your team spend hours copying data from emails into spreadsheets, from spreadsheets into accounting, and from accounting into reports, you are paying skilled people to act as glue. The Automation Sprint replaces one of those painful processes with a reliable, monitored workflow in two weeks. ### How the sprint works - Pick the process (day 1). We help you choose the process with the best return: frequent, rule-based, error-prone and annoying. - Map it (days 2–3). We document every step, exception and system involved, and agree on the target workflow. - Build it (days 4–8). Using the right tool for the job — native integrations, Zapier, Make, n8n, Power Automate or custom code with APIs. - Test it (days 9–10). With real data and edge cases, including what happens when something fails. - Hand it over. Documentation, a short training session and alerts so you know when the automation needs attention. ### What is included - One end-to-end workflow with up to five connected systems - Error handling, retries and notifications - Logging so every automated action can be traced - Process documentation and a recorded walkthrough - 30 days of support after go-live ### Examples of processes we automate - Invoice capture: email → data extraction → validation → accounting system → approval - Lead handling: web form → CRM → assignment → follow-up reminders - Order fulfilment: store order → warehouse pick list → shipping label → customer notification - Employee onboarding: HR form → accounts, licences, equipment request and welcome pack - Monthly reporting: data from several tools → dashboard → scheduled PDF to management ### Is it worth it? A process that takes 15 minutes, 20 times a week, costs around 260 hours a year. Automating it usually pays back the sprint within months — and removes copy-paste errors entirely. Our guide Business Process Automation: How to Find, Prioritise and Automate Repetitive Work shows how to calculate the return for your own processes. --- # Service: Cybersecurity Audit & Hardening URL: https://sisusoft.com/product/cybersecurity-audit/ A practical security review of your accounts, devices, network, website and backups, with a prioritised remediation plan and hands-on hardening of the critical gaps. Package: Audit & hardening ## Close the doors attackers actually use Most attacks on small businesses are not sophisticated. They succeed because of reused passwords, missing multi-factor authentication, unpatched devices, misconfigured email and backups that cannot be restored. The Cybersecurity Audit & Hardening package finds those gaps, explains them in plain language and fixes the most critical ones. ### What we review - Identity & accounts: MFA coverage, admin accounts, password policies, former employees' access, shared accounts - Email security: SPF, DKIM and DMARC records, phishing protection, forwarding rules, mailbox auditing - Devices: operating system versions, patch status, disk encryption, endpoint protection, local admin rights - Network & Wi-Fi: router and firewall configuration, guest network separation, remote access - Website & domain: CMS and plugin updates, TLS configuration, security headers, domain registrar lock - Cloud & SaaS: sharing settings in Microsoft 365 or Google Workspace, third-party app permissions - Backups & recovery: coverage, immutability, last successful restore test - People & process: incident response contacts, security awareness, supplier access ### Deliverables - A prioritised risk report (critical / high / medium / low) written for business owners, with a technical appendix - Hands-on hardening of critical findings within the package hours: for example enabling MFA, fixing DMARC, removing stale accounts - A 90-day remediation roadmap for the remaining items - A one-page incident response plan: who to call and what to do in the first hour - A 45-minute results presentation and Q&A ### Timeline Two to three weeks depending on the size of your environment (up to 25 users included). We need read-only admin access for the review and temporary admin access for hardening, which is removed afterwards. ### Optional add-ons - Phishing simulation and short staff training session - External vulnerability scan of public-facing systems - Quarterly follow-up reviews This is a practical security assessment, not a formal compliance certification or penetration test. We can recommend certified partners if you need those. Start with our free Small Business Cybersecurity Checklist. --- # The Secure Remote Work Toolkit: Tools, Policies and Habits for Distributed Teams URL: https://sisusoft.com/secure-remote-work-toolkit/ Published: 2026-10-21 Remote and hybrid work are now normal for many small businesses. The benefits are real — access to talent anywhere, fewer commutes, more focused work — but so are the challenges: information scattered across chat threads, laptops on home networks, unclear expectations and new security risks. The difference between a distributed team that thrives and one that struggles is rarely the video-call software. It is a deliberate combination of tools, policies and habits. This toolkit covers the essentials in six layers: identity, devices, collaboration, networks, policies and habits. ### Key takeaways - Identity is the new perimeter: single sign-on and MFA protect everything else. - Manage and encrypt every device that touches company data, including personal ones if you allow them. - Choose one home for each type of information and write it down. - A short written remote-work policy prevents most misunderstandings and many security incidents. - Asynchronous habits — clear writing, documented decisions — make distributed teams fast. ## Layer 1: Identity and access In an office, the network boundary used to be the main defence. In a distributed team, every login from every location is a potential entry point, so identity becomes the perimeter. - One identity per person in your productivity suite (Microsoft 365 or Google Workspace), used to sign in to other apps via single sign-on where possible. - Multi-factor authentication for everyone, with phishing-resistant methods (passkeys or security keys) for administrators. - Conditional access rules where available — for example blocking sign-ins from unmanaged devices or unexpected countries. - A business password manager for everything that cannot use single sign-on, with shared vaults per team. - Joiner-mover-leaver process: access granted by role, reviewed when roles change and removed on the last day. ## Layer 2: Devices Laptops and phones are now the office. Every device that accesses company data should be: - Enrolled in device management, so settings can be enforced and the device wiped if lost. - Encrypted (BitLocker on Windows, FileVault on macOS, default encryption on modern phones). - Automatically updated, with a supported operating system. - Protected by endpoint security software and a screen lock. - Used with a standard (non-administrator) account day to day. Company-owned or personal devices? Company-owned laptops are easier to secure and support. If you allow personal devices (BYOD), limit them to managed apps with data protection policies — for example allowing email and documents in managed apps that prevent copying data into personal apps — and make the rules clear in writing. ## Layer 3: Collaboration tools Remote teams drown when information lives everywhere. Decide where each type of information belongs: | | Information | Home | Examples | Quick questions, coordination | Team chat | Microsoft Teams, Slack, Google Chat | Formal and external communication | Email | Outlook, Gmail | Files and documents | Cloud storage with permissions | SharePoint/OneDrive, Google Drive | Tasks and projects | Project board | Planner, Asana, Trello, Jira, Linear | Knowledge and decisions | Wiki / handbook | Notion, Confluence, SharePoint pages | Meetings | Video calls with agendas and notes | Teams, Google Meet, Zoom Fewer tools, used consistently, beat many tools used inconsistently. Configure sharing defaults carefully: external sharing of files should be deliberate, links should expire, and sensitive folders should have restricted access. ## Layer 4: Home and travel networks - Change default router passwords and keep router firmware updated. - Use WPA3 or WPA2 encryption with a strong Wi-Fi passphrase. - Separate work devices from smart-home and guest devices where possible. - On public Wi-Fi, rely on HTTPS and, where your setup requires it, a company VPN or zero-trust access client; avoid accessing admin systems from untrusted networks. - Prefer cloud applications protected by identity and MFA over exposing office servers through remote desktop. ## Layer 5: Policies (keep them short) A two-page remote-work policy answers the questions people would otherwise guess at: - Working hours and availability: core collaboration hours, response-time expectations for chat and email. - Acceptable devices: company devices, BYOD rules, what may be installed. - Data handling: where files are stored, no company data on personal cloud accounts or USB drives, printing at home. - Physical security: lock screens, privacy in public places, secure storage of devices. - Incident reporting: how to report a lost device or suspicious email — immediately, without blame. - AI tools: which tools may be used with which data (see practical AI for small businesses). - Equipment and expenses: what the company provides or reimburses. ## Layer 6: Habits that make distributed teams fast - Write things down. Decisions, processes and context go into the shared knowledge base, not just into meetings. - Default to asynchronous. Use meetings for discussion and relationships; use writing for updates and information. - Clear requests. Every request states what is needed, by when and why. - Visible work. Tasks live on the shared board, so nobody needs to ask "what is the status?". - Meeting hygiene. Agenda in advance, notes and actions afterwards, recorded where appropriate. - Regular connection. Short check-ins, informal chats and occasional in-person time build trust. - Security as a habit. Report phishing, lock screens, verify payment changes by phone. ## Onboarding a remote employee: checklist - Device prepared, enrolled, encrypted and shipped before day one - Accounts created via the standard process, MFA set up on a guided call - Password manager access with team vaults - Access to the handbook, project board and relevant chat channels - Remote-work and security policies acknowledged - Short security awareness session - A buddy for the first weeks And for leavers: disable accounts, transfer file ownership, revoke sessions and tokens, recover or remotely wipe devices, and rotate any shared credentials they used. ## Frequently asked questions Do remote employees need a VPN?Not always. If all applications are cloud-based and protected by identity, MFA and device policies, a traditional VPN may be unnecessary. It is still useful for reaching on-premise resources or on untrusted networks. Should we allow personal devices?You can, with limits: managed apps, data protection policies and clear rules. For roles handling sensitive data, company-owned devices are safer. Which collaboration suite is best?Microsoft 365 and Google Workspace are both excellent. Choose based on your existing tools, file formats and your team's familiarity, then configure it well. How do we keep remote employees engaged?Clear goals, visible work, regular feedback, written communication and deliberate social time. Tools support culture but do not create it. ## Get your remote setup right Our Managed IT Support plan covers device management, identity and MFA, Microsoft 365 or Google Workspace administration and a helpdesk for remote staff. For a one-off review, our Cybersecurity Audit checks every layer in this toolkit. You may also find our cybersecurity checklist useful. --- # From Idea to MVP in 12 Weeks: A Founder’s Roadmap URL: https://sisusoft.com/build-mvp-12-weeks/ Published: 2026-09-16 A minimum viable product (MVP) is the smallest version of a product that lets you learn whether real people want it — and will use it, recommend it or pay for it. It is not a prototype that only works in a demo, and it is not version 1.0 with every feature on the wish list. It is a real, working product focused on one core job, built well enough that early users trust it. Twelve weeks is a realistic timeframe for many software MVPs when scope is disciplined. This roadmap shows how to use those weeks, what to decide when, and which corners you must never cut. ### Key takeaways - Define the one core problem and the one core user before writing any code. - Scope ruthlessly: every feature must support the main user journey or the learning goal. - Do not cut corners on security, data protection, backups or basic accessibility. - Build in two-week sprints with real user feedback, and decide on launch metrics up front. - Launch is the start of learning, not the finish line. ## Before week 1: validate the problem The most expensive MVP is one that solves a problem nobody has. Before committing budget, talk to at least 10–15 potential users. Ask about their current behaviour, not your idea: how do they solve the problem today, what does it cost them, what have they tried? Look for evidence of pain — workarounds, spending, frustration. If you can, test demand with a landing page, a waiting list or a manual "concierge" version of the service. ## Weeks 1–2: discovery and scope The goal of the first two weeks is a shared, written understanding of what will be built and why. - Problem statement: one sentence describing who has which problem and why it matters. - Primary user and core journey: the single path from sign-up to "aha moment" that the MVP must nail. - Success metrics: for example activation rate, weekly active users, conversion to paid, or task completion time. - Feature list with MoSCoW prioritisation: Must have, Should have, Could have, Won't have (this time). - Technical approach: platform (web, iOS, Android), stack, integrations and hosting — see how to choose a tech stack. - Risks and assumptions: what must be true for the product to succeed, and how the MVP will test it. A useful test for every feature: "If we leave this out, can the user still complete the core journey, and can we still learn what we need to learn?" If yes, it waits. ## Weeks 2–3: design Design starts with user flows and low-fidelity wireframes, then moves to a clickable prototype of the core journey. Put the prototype in front of five or so target users and watch them try it. Small usability tests at this stage catch problems that would cost far more to fix in code. Establish a simple design system — colours, typography, components — so development is consistent and fast. ## Weeks 3–10: build in four sprints Development runs in two-week sprints, each ending with a demo of working software on a staging environment. | | Sprint | Weeks | Typical focus | 1 | 3–4 | Foundations: project setup, CI/CD, authentication, data model, design system, first screens | 2 | 5–6 | Core journey part one: the main objects and actions users work with | 3 | 7–8 | Core journey part two: notifications, payments or integrations if they are must-haves | 4 | 9–10 | Admin panel, analytics events, polishing, performance and accessibility fixes Review priorities at the end of every sprint. New ideas will appear — add them to the backlog, not to the current sprint, unless something more important is removed. ## Weeks 11–12: test and launch - Quality assurance: functional testing of every must-have, cross-browser and device testing, and automated tests for critical flows. - Security review: authentication, authorisation (users can only see their own data), input validation, secrets management, dependency scanning. - Legal basics: privacy policy, terms of service, cookie consent where needed, and data processing agreements with your providers. - Operations: production hosting, backups, error tracking, uptime monitoring and alerts. - App stores: developer accounts, listings, screenshots and review submission for mobile apps — allow time for review. - Launch plan: who gets access first (often a closed beta), how you will onboard them and how they can give feedback. ## Corners you can cut — and ones you must not Fine to cut in an MVP - Advanced settings and customisation - Secondary user roles - Automation of rare admin tasks (do them manually) - Pixel-perfect animations - Support for every edge-case platform - Self-service for things you can handle by email Never cut - Security of accounts and data - Backups and the ability to restore - Privacy compliance and consent - Basic accessibility and mobile usability - Error tracking and monitoring - Clean, documented, version-controlled code ## After launch: measure, learn, iterate Launch is the beginning of the learning loop. In the first weeks: - Watch your success metrics daily and look at where users drop off in the core journey. - Talk to users — especially those who stopped using the product. - Fix friction in the core journey before adding new features. - Plan the next sprints based on evidence, not opinions. Decide in advance what result would make you pivot, persevere or stop. That decision is much easier to make before the launch emotions kick in. ## What an MVP costs Costs vary with complexity, platforms and integrations. A focused web or cross-platform mobile MVP built by a small experienced team typically sits in the range of a few months of a senior developer's cost — far less than a full product, and far more than a no-code prototype. Running costs at MVP scale (hosting, email, monitoring) are usually modest. Use our project cost estimator for a ballpark figure. ## No-code or code? No-code and low-code tools are excellent for validating ideas quickly, internal tools and landing pages. They can become limiting when you need complex logic, scale, specific integrations or full ownership of your intellectual property. A common path: validate with no-code or a concierge service, then build the MVP in code once demand is proven. ## Frequently asked questions Can an MVP really be built in 12 weeks?Yes, for a focused product with a clear core journey and a decisive product owner. Complex integrations, regulated data or many user roles extend the timeline. Web app or mobile app first?Choose where your users are and what the core journey needs. A responsive web app is fastest to iterate; cross-platform frameworks such as Flutter make iOS and Android feasible within an MVP budget. Who should own the code?You should, from day one, in a repository under your account. This protects your investment and makes it easy to grow the team later. What happens after the MVP?You iterate based on user data: improve the core journey, add the most-requested features and scale infrastructure as usage grows. ## Ready to build? Our fixed-price MVP Launch Package follows exactly this roadmap: discovery, design, four build sprints, QA and launch, with 30 days of support afterwards. Not sure whether your idea is ready? Start with a Discovery & Blueprint or book a free call. --- # Practical AI for Small Businesses: Where It Helps and Where It Does Not URL: https://sisusoft.com/practical-ai-small-business/ Published: 2026-08-12 Artificial intelligence has moved from research labs into everyday tools in a remarkably short time. Large language models can draft emails, summarise documents, answer questions, extract data and write code. For small businesses that is a real opportunity: tasks that once required hours of skilled work can be done in minutes. It is also a source of confusion, inflated promises and new risks. This article separates the useful from the hype. It covers where AI genuinely saves time for small businesses, where it falls short, how to manage the risks, and a simple 30-day plan to pilot it safely. ### Key takeaways - AI is strongest at language tasks: drafting, summarising, classifying, extracting and answering questions from your own documents. - It can produce confident but wrong answers, so keep humans in the loop for anything that matters. - Never put confidential or personal data into tools that may use it for training; use business plans with clear data terms. - Start with one narrow, measurable use case and expand from there. ## What modern AI is good at Today's generative AI models predict and generate text (and increasingly images, audio and code) based on patterns learned from vast amounts of data. In practice that makes them excellent at: - Drafting: first versions of emails, proposals, job descriptions, product descriptions and social posts. - Summarising: long documents, meeting transcripts, email threads and reports. - Transforming: changing tone, translating, simplifying technical language, reformatting data. - Classifying: routing support tickets, tagging feedback, detecting sentiment, sorting invoices. - Extracting: pulling structured data (names, dates, amounts) from unstructured text and documents. - Answering questions from a defined body of knowledge, such as your policies or product documentation. - Assisting with code and spreadsheets: formulas, scripts and small automations. ## Where it struggles - Factual accuracy without sources. Models can "hallucinate" — produce plausible but false statements, references or numbers. - Precise calculations and logic over many steps, unless connected to tools that compute. - Up-to-date knowledge, unless connected to search or your current data. - Judgement and accountability. Decisions about people, money, legal or health matters require human responsibility. - Consistency. The same prompt can produce different answers; production use needs guardrails and testing. ## Ten practical use cases for small businesses | | Area | Use case | Human role | Customer service | Draft replies to common questions from your knowledge base | Review and send; handle complex cases | Customer service | Classify and route incoming tickets and emails | Check misrouted items | Sales | Summarise calls and draft follow-up emails | Edit and personalise | Sales | Research prospects from public information | Verify before using | Marketing | First drafts of articles, product descriptions and posts | Fact-check, add expertise, edit voice | Finance & admin | Extract data from invoices and receipts | Approve; review exceptions | Operations | Internal assistant that answers questions from policies and manuals | Maintain the source documents | HR | Draft job descriptions and onboarding material | Ensure fairness and accuracy | Management | Summarise reports and meeting notes into actions | Decide priorities | IT | Help write scripts, formulas and automations | Test before production use ## Three levels of adoption ### Level 1: AI assistants for individuals Employees use a business-grade AI assistant (included in many productivity suites or available as a standalone subscription) for drafting and summarising. Low cost, quick wins, but benefits depend on individual habits. Provide a short policy and training. ### Level 2: AI inside your existing tools Many CRMs, helpdesks, accounting and document tools now include AI features. Turning them on — with appropriate settings — brings AI into workflows without custom development. ### Level 3: Custom AI workflows AI connected to your own data and processes: an assistant that answers questions from your documents (often called retrieval-augmented generation), a pipeline that extracts and validates data from documents, or a classifier that routes requests. This is where the biggest gains are, and where good engineering matters most. It pairs naturally with business process automation. ## Managing the risks ### Data privacy and confidentiality Read the data terms of every AI tool. Consumer versions may use your inputs to improve models; business plans usually offer contractual commitments not to train on your data, plus retention controls. Do not paste personal data, client secrets, passwords or proprietary code into tools without such commitments. Check whether processing personal data with an AI service requires updates to your privacy notice or a data processing agreement. ### Accuracy Design workflows so that AI output is reviewed before it reaches customers or affects money, and ground answers in your own sources with citations where possible. Measure error rates on real examples before scaling. ### Security AI systems that read external content (emails, web pages, documents) can be manipulated by hidden instructions — so-called prompt injection. Limit what automated AI agents are allowed to do, require approval for consequential actions, and keep access permissions minimal. ### Intellectual property and transparency Be careful with AI-generated content that may resemble copyrighted work, and review generated code for licence and security issues. Consider telling customers when they are interacting with an AI assistant, and always offer a route to a human. ### Regulation AI regulation is evolving, for example the EU AI Act and various US state laws. Most small-business uses are low-risk, but uses that affect hiring, credit or access to services can carry specific obligations. Seek qualified legal advice when in doubt. ## A 30-day AI pilot plan - Week 1 — choose one use case. Pick a frequent, language-heavy task with a measurable outcome, such as drafting replies to the 20 most common customer questions. - Week 1 — set rules. Agree which tool, which data may be used, who reviews output and how results are measured. - Week 2 — prepare the knowledge. Collect and clean the documents the AI should rely on. Outdated or contradictory documents produce bad answers. - Week 3 — run the pilot. A small group uses the workflow daily and records time spent, edits needed and errors. - Week 4 — evaluate. Compare with the baseline. Keep, adjust or stop. If it works, document it and plan the next use case. ## Estimating the return Keep the calculation simple: hours saved per week × hourly cost × 48 weeks, minus subscription and setup costs. Include quality effects — faster response times, fewer errors — even if they are harder to quantify. Be sceptical of vendor claims; your own pilot data is what counts. ## Frequently asked questions Will AI replace jobs in small businesses?In most small businesses AI changes tasks rather than eliminating roles. It removes routine writing and data work so people can focus on customers, judgement and relationships. Is it safe to use AI with customer data?It can be, with business-grade tools that commit not to train on your data, appropriate contracts, minimal data sharing and human review. Avoid consumer tools for confidential data. Do we need our own AI model?Almost never. Using established models through secure business services and connecting them to your own data is far cheaper and more effective for small businesses. How do we stop AI from making things up?Ground it in your own documents, ask it to cite sources, restrict it to answering from those sources, and keep a human in the loop for important outputs. ## Where to start Pick one task that eats hours every week and run a 30-day pilot. If you want help designing a safe AI workflow — connected to your systems, with guardrails and measurable results — we build them as part of our automation and custom software services. Tell us what you would like to try. --- # The 3-2-1 Backup Rule and a Disaster Recovery Plan That Actually Works URL: https://sisusoft.com/backup-disaster-recovery-plan/ Published: 2026-07-08 Almost every business says it has backups. Far fewer can say how long it would take to restore everything after a ransomware attack, a failed server or an accidentally deleted folder — or when they last actually tried. A backup you have never restored is a hope, not a plan. This guide explains the modern 3-2-1-1-0 backup rule, how to set realistic recovery targets, what to back up (including cloud services people often forget) and how to write a disaster recovery plan that your team can follow under pressure. ### Key takeaways - Define RPO (how much data you can lose) and RTO (how long you can be down) for each system before choosing tools. - Follow 3-2-1-1-0: three copies, two media, one off-site, one immutable or offline, zero restore errors. - SaaS data in Microsoft 365, Google Workspace and similar tools also needs backup. - Test restores on a schedule and write the results down. - Keep the disaster recovery plan short, printed and known to the people who will use it. ## Backup is not the same as disaster recovery Backup is a copy of data you can restore. Disaster recovery (DR) is the process and infrastructure that bring the business back to operation after a serious incident: restoring data, rebuilding systems, re-establishing access and communicating with staff and customers. Business continuity is wider still: how the business keeps operating at all while systems are down. You need backups to do DR, but backups alone do not guarantee a quick recovery. ## Step 1: Set recovery targets — RPO and RTO - Recovery Point Objective (RPO): the maximum amount of data, measured in time, you can afford to lose. An RPO of 24 hours means a daily backup is acceptable; an RPO of 15 minutes requires much more frequent copies or replication. - Recovery Time Objective (RTO): the maximum time a system can be unavailable before the impact becomes unacceptable. Set these per system, together with the people who use them, and be honest about cost: shorter RPO and RTO cost more. | | System | Example RPO | Example RTO | Typical approach | Accounting / ERP database | 1 hour | 4 hours | Frequent database backups + documented rebuild | Email & documents (SaaS) | 24 hours | 8 hours | Third-party SaaS backup with granular restore | E-commerce website | 1 hour | 2 hours | Database + files backup, infrastructure-as-code | File archive | 24 hours | 2 days | Daily backup to cloud storage | Employee laptops | 24 hours | 1 day | Data in cloud storage, device re-imaging ## Step 2: Apply the 3-2-1-1-0 rule The classic 3-2-1 rule has been extended to address ransomware: - 3 copies of your data (the original plus two backups) - 2 different types of storage (for example a local appliance and cloud object storage) - 1 copy off-site, in a different location or region - 1 copy immutable or offline — it cannot be changed or deleted, even by an administrator account, for a set retention period - 0 errors in your most recent restore test The immutable copy is the one that saves you when attackers gain administrator access and try to delete backups before encrypting your systems. Most modern backup tools and cloud storage services offer object lock or immutability features. ## Step 3: Know what to back up - Databases of line-of-business applications, using application-consistent methods. - File shares and document libraries. - SaaS data: email, OneDrive/SharePoint, Google Drive, CRM, accounting exports. Providers keep their service running, but under the shared responsibility model they generally do not protect you against deletion by a user, a malicious insider or a compromised account beyond limited retention windows. - Websites: database, uploaded media, themes and plugins or application code. - Configuration: firewall and router settings, DNS records, cloud infrastructure definitions, licence keys. - Credentials and documentation needed for recovery, stored securely and accessible during an outage (for example in a password manager with emergency access). ## Step 4: Choose retention A common scheme keeps daily backups for 30 days, weekly backups for three months and monthly backups for one year. Adjust for legal retention requirements and for the fact that some attacks or data errors are discovered weeks later. Remember that backups containing personal data are subject to the same privacy obligations as the original data. ## Step 5: Protect the backups themselves - Use separate credentials for the backup system, protected by MFA, not linked to your everyday admin accounts. - Encrypt backups at rest and in transit, and store the keys safely. - Enable immutability or keep an offline copy. - Monitor backup jobs and alert on failures — a silent failure for three months is common. ## Step 6: Test restores regularly Schedule restore tests and record the results: - Monthly: restore a few random files and a mailbox item. - Quarterly: restore a complete database or virtual machine into an isolated environment and verify the application works. - Annually: run a tabletop or full DR exercise based on a realistic scenario, such as ransomware on the main server. Measure how long each restore takes and compare it with your RTO. If restoring 2 TB from cloud storage takes 30 hours and your RTO is 8, you need a different approach — for example a local copy for fast restores plus the cloud copy for disasters. ## Step 7: Write the disaster recovery plan A good DR plan is short enough to be used under stress. Include: - Roles and contacts: who leads, who decides, IT partner, key vendors, insurer, bank, legal advisor — with phone numbers. - Triggers: what counts as a disaster and who declares it. - Priorities: the order in which systems are restored, based on RTO. - Procedures: step-by-step restore instructions for each critical system, with where backups and credentials are. - Communication: templates for staff, customers and suppliers, and an alternative channel if email is down. - Workarounds: how the business keeps operating manually while systems are restored. - After-action review: how you will learn and improve after an incident. Store the plan in several places, including on paper. If your systems are encrypted, a plan stored only on the file server is useless. ## Ransomware-specific considerations - Isolate infected systems quickly, but preserve evidence. - Restore into a clean environment; attackers often remain in the network for a while before encrypting, so check backups for persistence mechanisms. - Reset all credentials, starting with administrators, from clean devices. - Check legal notification duties if personal data may have been accessed. - Prevention matters most: see our cybersecurity checklist. ## A simple DR plan template 1. Incident lead: name, phone · Deputy: name, phone2. IT partner: company, 24/7 number · Insurer: policy no., hotline3. Restore priority: (1) identity & email, (2) accounting, (3) website/shop, (4) file shares4. Backup locations: local appliance (office), cloud storage (region), immutable copy (retention 30 days)5. Credentials: password manager emergency access held by lead and deputy6. Communication: staff via phone tree / messaging group; customers via website banner and template email7. Last full test: date, duration, issues found, actions ## Frequently asked questions Is cloud sync (OneDrive, Dropbox, Google Drive) a backup?Not on its own. Sync replicates deletions and encrypted files too. Version history helps, but a separate backup with independent retention is still recommended. How often should we back up?As often as your RPO requires. Daily is a common minimum; critical databases often need hourly or continuous protection. How long does a restore take?It depends on data volume, bandwidth and storage type. Measure it in a test — that number is far more useful than any estimate. Do we need a DR plan if everything is in the cloud?Yes. Accounts can be compromised, data can be deleted and providers can have outages. The plan may be simpler, but it is still needed. ## Need help? Backup monitoring and quarterly restore tests are part of our Managed IT Support plans, and our Cloud Migration & DevOps assessment includes a backup and DR design with defined RPO and RTO. Contact us if you would like someone to check whether your backups would really save you. --- # How to Choose a Tech Stack for Your Web Application URL: https://sisusoft.com/choosing-tech-stack-web-application/ Published: 2026-06-17 Few technical decisions attract as many strong opinions as the choice of a tech stack. Every framework has passionate fans, and every month brings a new tool that promises to change everything. For a business building a web application, though, the goal is not to use the most fashionable technology. It is to ship a reliable product, hire people who can work on it, and keep maintenance costs reasonable for years. This guide walks through the layers of a modern web application and gives practical, non-hype criteria for each choice. ### Key takeaways - Choose mature, well-documented technologies with large talent pools — "boring" is a feature. - Your team's existing skills are often the strongest argument for a stack. - A relational database such as PostgreSQL is the right default for most business applications. - Start with a well-structured monolith; split into services only when there is a clear reason. - Budget for operations — hosting, monitoring, backups and updates — from day one. ## What "tech stack" means A tech stack is the combination of technologies used to build and run an application. For a typical web application it includes: - Frontend: what runs in the browser — HTML, CSS and JavaScript, usually with a framework. - Backend: the server-side language and framework that implement business logic and APIs. - Database: where data is stored and queried. - Infrastructure: hosting, containers, networking, file storage. - Tooling: version control, testing, CI/CD, monitoring, error tracking. - Third-party services: authentication, payments, email, search, analytics. ## The criteria that actually matter - Fit for the problem. A content-heavy marketing site, a real-time collaboration tool and a data-processing back office have different needs. - Team skills. A team that is excellent in one ecosystem will outperform the same team learning a "better" one. - Talent availability. Can you hire or contract developers for this stack in your budget, now and in five years? - Maturity and ecosystem. Stable releases, long-term support, security updates, libraries and documentation. - Total cost. Licences, hosting requirements and developer productivity. - Security track record. Secure defaults, active security team, quick patches. - Performance and scalability. Important, but rarely the bottleneck for business applications at launch. Clean architecture matters more than raw speed. ## Frontend choices For most interactive applications, a component-based JavaScript framework is the norm. React has the largest ecosystem and talent pool; Vue is approachable and productive; Svelte and others are elegant with smaller communities; Angular is opinionated and popular in enterprise settings. Meta-frameworks such as Next.js or Nuxt add routing, server-side rendering and performance features that help with SEO. Not every application needs a heavy single-page app. Server-rendered pages enhanced with small amounts of JavaScript (for example with htmx or Alpine.js, or a framework's built-in server components) are fast, accessible and simpler to maintain for many internal tools and content sites. Whatever you choose, insist on accessibility (WCAG 2.2 AA), responsive design and performance budgets from the start — retrofitting them is expensive. ## Backend choices | | Stack | Strengths | Typical use | PHP / Laravel | Very productive, batteries included, huge hosting availability | Business apps, portals, SaaS, e-commerce | Node.js (Express, NestJS) | JavaScript end-to-end, good for real-time and APIs | APIs, real-time features, full-stack JS teams | Python (Django, FastAPI) | Readable, strong in data and AI, mature admin tooling | Data-heavy apps, AI integration, internal tools | Ruby on Rails | Convention over configuration, rapid development | Start-up products, CRUD-heavy apps | C# / .NET | Performance, strong typing, Microsoft ecosystem | Enterprise apps, Azure-centric organisations | Java / Kotlin (Spring) | Robust, scalable, enterprise-grade tooling | Large systems, regulated industries | Go | Fast, simple concurrency, small binaries | High-throughput services, infrastructure tools All of these are proven in production. The differences that matter most for a small or mid-sized business are team familiarity, productivity of the framework (authentication, admin, migrations, queues out of the box) and the availability of developers. ## Database choices For most business applications, a relational database is the right default. PostgreSQL is an excellent general-purpose choice: reliable, standards-compliant, feature-rich (including JSON storage and full-text search) and available as a managed service on every major cloud. MySQL/MariaDB is also solid and widely supported. Document databases such as MongoDB suit some use cases with highly variable data structures. Specialised stores — Redis for caching and queues, a search engine for complex search, a time-series database for metrics — are added when there is a specific need, not by default. ## Architecture: start with a modular monolith Microservices solve real problems for large organisations with many teams. For most new applications they add complexity — networking, deployment, data consistency, monitoring — without corresponding benefits. A well-structured monolith with clear modules is faster to build, easier to test and cheaper to run. If one part later needs to scale independently, it can be extracted into a service. ## Hosting and infrastructure - Platform-as-a-service (managed app hosting) lets you deploy without managing servers — ideal for small teams. - Containers (Docker) make environments consistent from a developer's laptop to production. - Managed databases handle backups, updates and failover for you. - Infrastructure-as-code (for example Terraform) makes environments reproducible and reviewable. - Serverless functions are useful for event-driven tasks and spiky workloads, but can complicate local development and debugging. Our cloud migration guide covers cost modelling and security for these choices. ## Tooling you should not skip - Git with a hosted repository that you own - Automated tests (unit, integration and a few end-to-end tests for critical journeys) - Continuous integration that runs tests and security scans on every change - Automated deployments to staging and production - Error tracking and uptime monitoring with alerts - Dependency updates and vulnerability scanning - Secrets management — no passwords in code ## Build or buy individual components Do not build what is not your core value. Authentication, payments, transactional email, file storage, search and analytics are best handled by mature libraries or services. Spend your custom development budget on the parts that make your product unique. ## Example stacks for common scenarios | | Scenario | A sensible stack | Internal business tool for 20–200 users | Laravel or Django, server-rendered UI with light JavaScript, PostgreSQL, managed hosting | Customer-facing SaaS MVP | React/Next.js or Vue/Nuxt frontend, Node.js or Laravel API, PostgreSQL, managed cloud services | Content-heavy site with a shop | WordPress + WooCommerce or a headless CMS, with custom plugins for unique features | Mobile app with web admin | Flutter or React Native app, Laravel/Node.js API, PostgreSQL, web admin panel | Data or AI-centric application | Python (FastAPI/Django), PostgreSQL, task queue, managed AI APIs ## Frequently asked questions What is the best tech stack in 2026?There is no single best stack. The best one for you is mature, fits your problem, matches your team's skills and has a large talent pool. Several stacks meet those criteria equally well. Should we use the newest framework?Usually not for a business-critical application. New frameworks can be excellent, but they carry more risk: fewer developers, fewer libraries and more breaking changes. Can we change the stack later?Parts of it, yes — especially if the architecture is modular and APIs are clean. Rewriting everything is expensive, so choose deliberately at the start. Is WordPress a real application platform?For content-driven sites, membership and e-commerce, WordPress with WooCommerce is a proven and cost-effective choice. For complex business logic, a dedicated application framework is usually cleaner. ## Conclusion Choose technology like you would choose a business partner: for reliability, track record and long-term fit, not for hype. If you would like an independent recommendation for your project, our Discovery & Blueprint includes an architecture and hosting plan, and our MVP Launch Package turns it into a product. Planning an MVP? Read From Idea to MVP in 12 Weeks. --- # Custom Software vs Off-the-Shelf: A Practical Decision Framework URL: https://sisusoft.com/custom-vs-off-the-shelf-software/ Published: 2026-05-27 Sooner or later every growing business faces the question: should we buy a ready-made software product, or build something tailored to us? Vendors of both options have obvious incentives to give you a one-sided answer. The honest answer is that it depends — but it depends on a small number of factors you can assess yourself. This article gives you a practical framework: what each option really costs over time, where each one shines, a simple scoring model and three realistic scenarios. It also introduces the option that is often best of all: buy, then extend. ### Key takeaways - Buy when the process is standard and not a source of competitive advantage. - Build when the process is unique, central to how you win, or when combining several tools costs more than one tailored system. - Compare total cost of ownership over three to five years, not just the first-year price. - "Buy and extend" — a standard platform plus custom integrations — is frequently the best balance. ## The two options, honestly ### Off-the-shelf software (SaaS or packaged) Advantages: available immediately, predictable subscription cost, the vendor handles hosting, security and updates, and you benefit from features requested by thousands of other customers. Documentation, training material and experienced users are easy to find. Disadvantages: you adapt your process to the software; features you need may never arrive; per-user prices grow with your team; integrations may be limited; your data lives in the vendor's format; and price increases or product changes are outside your control. ### Custom software Advantages: fits your exact process, can encode what makes you different, integrates precisely with your other systems, has no per-user licence cost, and you own the code and the roadmap. Disadvantages: higher upfront investment, takes time to build, requires ongoing maintenance and hosting, and its quality depends heavily on who builds it. ## Total cost of ownership: compare apples with apples A common mistake is comparing a monthly subscription with a one-off development price. Instead, estimate the full cost over three to five years for both options: | | Cost element | Off-the-shelf | Custom | Initial cost | Setup, configuration, data migration | Discovery, design, development, migration | Recurring licences | Per user or per tier, usually rising over time | Usually none (open-source stack) | Hosting & operations | Included | Hosting, monitoring, backups | Maintenance | Included in subscription | Updates, security patches, small changes | Integrations | Connectors, middleware, workarounds | Built in, but must be maintained | Hidden costs | Manual workarounds, extra tools to fill gaps, training | Knowledge transfer, documentation | Exit cost | Data export, migration, retraining | Low if you own code and data The most underestimated line is "manual workarounds". If people spend five hours a week compensating for a tool that does not fit — exporting, re-typing, reconciling — that is roughly 240 hours a year. Put a cost on that time before deciding. ## A simple scoring framework Score your situation from 1 (strongly favours buying) to 5 (strongly favours building) on each question: - Uniqueness: how different is your process from industry standard practice? - Strategic value: does this process directly differentiate you from competitors? - Fit of available products: how much would you need to change your process to fit the best product? (More change = higher score.) - Integration needs: how many systems must it connect with, and how deeply? - Scale economics: how many users will it have in three years? (Many users on per-seat pricing = higher score.) - Time pressure: how soon do you need it? (Urgent = lower score.) - Ability to maintain: do you have, or can you contract, a reliable team to maintain it? (No = lower score.) Add the scores. 7–15: buy. 16–25: buy and extend, or build a narrow custom component. 26–35: custom software is likely the better long-term investment. Treat the result as a conversation starter, not an oracle — but it forces the right questions. ## The third option: buy, then extend Many of the best solutions combine both approaches. You use a strong standard product for what it does well — accounting, email, CRM, e-commerce — and add custom components where your business is different: - A custom integration that synchronises orders between your shop and your warehouse system - A pricing or quoting engine that feeds the CRM - A customer portal on top of your existing back-office system - A reporting layer that combines data from several products This keeps the custom code small, focused and cheaper to maintain, while you still benefit from the vendor's investment in the standard parts. ## Three scenarios ### Scenario A: a 12-person accounting practice needs a CRM The sales and client-management process is fairly standard, the team is small and they need it next month. Recommendation: buy a mainstream CRM, configure it well and automate a few integrations with the practice management system. ### Scenario B: a logistics company with unusual routing rules Dispatch depends on vehicle types, customer time windows, special handling and driver qualifications. Off-the-shelf tools handle 70% and staff fix the rest in spreadsheets daily. Efficient dispatch is a key competitive advantage. Recommendation: build a custom dispatch tool, integrated with the existing accounting and telematics systems. ### Scenario C: an online retailer with complex product bundles A standard e-commerce platform works well for the storefront and payments, but bundle pricing and stock allocation are unique. Recommendation: buy and extend — keep the platform, build a custom bundling and stock service connected via API. ## Questions to ask before you decide - What exactly is the problem, and what does it cost us today? - Have we trialled the two or three best products with real data and real users? - What will this cost over five years, including our own time? - What happens to our data if the vendor raises prices, is acquired or shuts down? - If we build, who will maintain it, and is the code in a repository we own? - Can we start smaller — one module, one integration — and expand later? ## Red flags on both sides When buying: no data export, no API, long lock-in contracts, per-user pricing that makes growth painful, and a roadmap that ignores the features you need. When building: no discovery phase, fixed price without a clear scope, code owned by the vendor, obscure technologies, no automated tests, no documentation and no plan for maintenance. ## Frequently asked questions Is custom software always more expensive?Upfront, usually yes. Over three to five years, not necessarily — especially with many users on per-seat pricing or when off-the-shelf tools force costly manual workarounds. How long does custom software take to build?Focused tools often take four to ten weeks; larger platforms are delivered in phases, with a first useful release typically within three months. Can we switch from off-the-shelf to custom later?Yes, if you keep your data exportable. Many companies start with a standard product and build custom components once they understand their needs better. What is the biggest risk of custom software?Dependence on a single developer. Mitigate it with code ownership, documentation, tests and mainstream technology choices. ## Get an independent recommendation We are happy to recommend an off-the-shelf product when it is the right choice — it happens often. Our Discovery & Blueprint evaluates options objectively, prototypes the custom route if it makes sense, and gives you a fixed price to compare. For inspiration on what custom tools can do, see 12 Everyday Business Problems Custom Software Can Solve. --- # Business Process Automation: How to Find, Prioritise and Automate Repetitive Work URL: https://sisusoft.com/business-process-automation-guide/ Published: 2026-05-06 Automation has a reputation problem. Some people imagine robots replacing staff; others have seen a "quick automation" break silently and corrupt a month of data. In reality, good business process automation is unglamorous: it removes repetitive, rule-based work from people's days, reduces errors and makes processes faster and more predictable. The key is choosing the right processes and building automations that are reliable and visible. This guide gives you a repeatable method: find candidates, score them, design the workflow, choose the tool, build with error handling and measure the results. ### Key takeaways - The best first automation is frequent, rule-based, stable and painful — not the most impressive one. - Map and simplify the process before you automate it; automating a bad process just produces bad results faster. - Every automation needs an owner, logging, error alerts and documentation. - Measure time saved and error rates before and after, so you know the return. ## What business process automation is (and is not) Business process automation (BPA) uses software to perform steps of a business process without manual intervention: moving data between systems, creating documents, sending notifications, routing approvals or updating records. It ranges from a simple rule in your email client to multi-step workflows across accounting, CRM, e-commerce and storage systems. It is not about removing people from decisions. The most effective automations handle the predictable 80% of cases and route the exceptions to a human with all the context they need. ## Step 1: Find automation candidates Ask your team a simple question: "What do you do every week that feels like copying and pasting?" You will get a long list. Common answers include: - Entering invoices or receipts from email into accounting software - Copying web leads into the CRM and assigning them - Creating projects, folders and tasks when a deal is won - Sending reminders for overdue invoices, renewals or appointments - Generating contracts, quotes or certificates from templates - Updating stock levels across sales channels - Compiling weekly or monthly reports from several tools - Onboarding and offboarding employees Look also at process data: where do errors occur, where do tasks wait, and which steps generate complaints? ## Step 2: Score and prioritise Score each candidate from 1 to 5 on these criteria: | | Criterion | Question | Why it matters | Volume | How often does it happen? | Frequent tasks generate the biggest savings | Time per run | How long does it take manually? | Multiplies with volume | Rules | Can the decisions be written down as rules? | Judgement-heavy steps are hard to automate | Stability | Does the process change often? | Moving targets break automations | Error cost | What does a mistake cost? | Automation removes typos and omissions | Systems | Do the systems have APIs or integrations? | Determines effort and reliability Then estimate the annual time cost: runs per week × minutes per run × 48 working weeks ÷ 60. A task that takes 12 minutes and happens 25 times a week costs 240 hours a year. Put a value on those hours — including the opportunity cost of what skilled people could do instead — and compare it with the cost of automating. Start with the candidate that has the highest score and a clear return. ## Step 3: Map and simplify the process Before building anything, document how the process works today, step by step, including the exceptions people handle without thinking. Then ask: - Which steps add no value and can be removed? - Where is the same data entered more than once? - Which decisions are rules (if amount > X, then approval by Y) and which need judgement? - What should happen when data is missing or invalid? - Who needs to know when the process completes or fails? Often, simplifying the process removes a third of the work before any automation is built. ## Step 4: Choose the right tool | | Approach | Examples | Best when | Built-in features | Rules and workflows inside your CRM, accounting or helpdesk | The process lives mostly in one system | No-code integration platforms | Zapier, Make, Power Automate | Connecting popular SaaS tools with moderate volume | Open-source / self-hosted workflow engines | n8n and similar | Higher volume, data residency requirements, cost control | Custom code | Small services using APIs and webhooks | Complex logic, high volume, unusual systems | RPA (screen automation) | Desktop robots that click through interfaces | Last resort for legacy systems without APIs Prefer APIs over screen automation whenever possible: APIs are faster and far more reliable. Consider running costs too — per-task pricing on no-code platforms can become significant at high volume. ## Step 5: Build for reliability An automation that fails silently is worse than no automation, because people stop checking. Build every workflow with: - Validation: check inputs before acting (is the invoice total a number, does the customer exist?). - Idempotency: running the same event twice should not create duplicates. - Error handling and retries: temporary failures are retried; persistent failures go to a queue for a human. - Alerts: the owner is notified by email or chat when something fails. - Logging: every action is recorded so you can answer "what happened to order 1042?". - Security: use service accounts with minimal permissions and store credentials securely, never in plain text. ## Step 6: Test, launch and document Test with real historical data and with deliberately broken inputs. Run the automation in parallel with the manual process for a short period if the stakes are high. Document what the automation does, which accounts it uses, who owns it and how to pause it. Train the people affected — they need to know what changed and how to handle exceptions. ## Step 7: Measure and iterate Compare before and after: processing time, error rates, backlog and employee satisfaction. Review the automation's logs monthly for failures and edge cases. Then pick the next candidate from your list. Automation compounds: each workflow makes the next easier because the integrations and patterns already exist. ## A worked example: invoice processing A distributor receives around 120 supplier invoices a month by email. An administrator downloads each PDF, types supplier, date, amounts and tax into the accounting system and forwards it for approval — about 8 minutes per invoice, or roughly 190 hours a year, with occasional typos. The automated workflow: invoices sent to a dedicated mailbox are picked up automatically; data is extracted from the PDF; totals and supplier details are validated against existing records; a draft bill is created in the accounting system with the PDF attached; invoices above a threshold are routed for approval; anything that fails validation lands in an exceptions list. The administrator now reviews exceptions instead of typing every invoice — the work drops to a fraction of the original time, and transcription errors disappear. ## Common pitfalls - Automating a broken process instead of fixing it first. - Building everything in one person's personal account — when they leave, the automations break. - No monitoring, so failures are discovered by customers. - Over-automating judgement calls that need a human. - Ignoring change management: people need to trust the new workflow. ## Frequently asked questions Will automation replace our employees?In small businesses automation usually removes tasks, not jobs. It frees people from repetitive work so they can focus on customers, quality and growth. How much does an automation cost?Simple integrations can be set up in hours; multi-system workflows with error handling typically take one to two weeks. Our fixed-price Automation Sprint covers one end-to-end workflow. What if one of our systems has no API?Look for import/export features, email-based integrations or a database connection. Screen automation (RPA) is a last resort because it breaks when the interface changes. Can AI help with automation?Yes, especially for unstructured inputs such as emails and documents. Combine AI extraction with validation rules and human review for exceptions. See our article on practical AI. ## Start with one process Pick the most annoying repetitive task in your business and calculate what it costs per year. If the number surprises you, it is time to automate. Our two-week Automation Sprint maps, builds, tests and documents one complete workflow at a fixed price. For ideas on combining automation with AI, read Practical AI for Small Businesses. --- # Small Business Cybersecurity Checklist: 15 Controls That Stop Most Attacks URL: https://sisusoft.com/small-business-cybersecurity-checklist/ Published: 2026-04-15 Small businesses often assume they are too small to be a target. Attackers disagree. Automated tools scan the entire internet for weak passwords, unpatched software and misconfigured email every day, and they do not care about company size. A small business usually has valuable data — customer details, bank access, invoices — and fewer defences than a large one. The good news: most successful attacks exploit a short list of missing basics. Fix those, and you become a much harder target than the majority of businesses. This checklist contains fifteen controls, grouped by priority, with plain-language explanations of why each one matters. ### Key takeaways - Multi-factor authentication, patching and tested backups stop a large share of common attacks. - Email is the main entry point: configure SPF, DKIM and DMARC and train people to spot phishing. - Know what you have — devices, accounts, data — or you cannot protect it. - Write a one-page incident plan before you need it. - Security is a habit, not a project: review quarterly. ## Priority 1: Do these this month ### 1. Turn on multi-factor authentication (MFA) everywhere Stolen and reused passwords are among the most common ways into a business. MFA adds a second proof of identity — an authenticator app, a security key or a passkey — so a stolen password alone is not enough. Start with email, Microsoft 365 or Google Workspace, banking, your domain registrar, your website admin and any remote access. Prefer authenticator apps or hardware keys over SMS codes, and protect administrator accounts with the strongest method available. ### 2. Use a password manager People reuse passwords because remembering dozens of unique ones is impossible. A business password manager generates and stores strong, unique passwords, lets you share credentials securely with colleagues and removes access instantly when someone leaves. ### 3. Keep everything updated Attackers exploit known vulnerabilities, often within days of a patch being released. Enable automatic updates for operating systems, browsers and applications; update routers, firewalls and printers; and keep your website's CMS, themes and plugins current. Replace devices and software that no longer receive security updates. ### 4. Back up with the 3-2-1-1-0 rule — and test restores Ransomware encrypts your data and often tries to delete backups too. Keep at least three copies of data, on two types of storage, one off-site, one immutable or offline, and with zero errors in your last restore test. Cloud services like Microsoft 365 and Google Workspace also need backups: the provider keeps the service running, but protecting your data from deletion or encryption is your responsibility. Our backup and disaster recovery guide explains how to set this up. ### 5. Secure your email domain Configure SPF, DKIM and DMARC records for your domain. Together they make it much harder for criminals to send emails that appear to come from you — a common trick in invoice fraud. Start DMARC in monitoring mode, review the reports and gradually move to a policy that rejects spoofed messages. ## Priority 2: Do these this quarter ### 6. Train people to recognise phishing Technology filters a lot, but some phishing emails will always reach inboxes. Short, regular training — with real examples and no blame — teaches people to check sender addresses, hover over links, be suspicious of urgency and verify payment changes by phone using a known number. Make reporting suspicious messages easy and celebrate it. ### 7. Protect every device Every laptop and phone that accesses company data should have disk encryption, a screen lock, current updates and endpoint protection. Use a device management tool to enforce these settings and to wipe a lost device remotely. Users should not work with local administrator rights day to day. ### 8. Apply least privilege Give people access only to what they need for their role. Separate administrator accounts from everyday accounts. Review access quarterly and immediately when roles change. Remove former employees' and suppliers' access on their last day — a step that is forgotten surprisingly often. ### 9. Secure your network and Wi-Fi Change default router passwords, use WPA3 or at least WPA2 with a strong passphrase, keep a separate guest network for visitors and smart devices, and close remote-access ports that are exposed to the internet. Remote access should go through a VPN or identity-aware access with MFA. ### 10. Harden your website Your website is public by definition. Keep it updated, use strong admin passwords with MFA, limit login attempts, run a web application firewall, enable HTTPS everywhere, add security headers, take regular backups and lock your domain at the registrar. For WordPress sites, remove unused plugins and themes. ## Priority 3: Build lasting habits ### 11. Keep an inventory of assets and data Maintain a list of devices, software, cloud services, accounts and where sensitive data is stored. You cannot protect what you do not know you have, and the inventory makes onboarding, offboarding and incident response much faster. ### 12. Control payment changes Business email compromise often ends with a request to change bank details or pay an "urgent" invoice. Require a call-back to a known phone number and approval by a second person for any change in payment details or unusual transfer. ### 13. Review third-party access and apps Suppliers, contractors and connected apps often have broad access to your systems. Review which external apps can read your email, files or calendars, remove the ones you no longer use and ensure suppliers protect their accounts with MFA. ### 14. Write a one-page incident response plan When something goes wrong, panic wastes precious time. Write down who to call (internal lead, IT partner, bank, insurer, legal advisor), how to isolate affected devices, where backups are and how to communicate with staff and customers. Print it — if your systems are encrypted, you will not be able to open the document. ### 15. Review security quarterly Schedule a short quarterly review: check MFA coverage, outdated devices, access lists, backup tests, DMARC reports and any incidents. Small, regular attention prevents the slow drift back to insecurity. ## The checklist at a glance | | # | Control | Priority | Effort | 1 | MFA on all accounts | Critical | Low | 2 | Password manager | Critical | Low | 3 | Automatic updates | Critical | Low | 4 | 3-2-1-1-0 backups + restore test | Critical | Medium | 5 | SPF, DKIM, DMARC | High | Low | 6 | Phishing awareness | High | Low | 7 | Device encryption & management | High | Medium | 8 | Least privilege & access reviews | High | Medium | 9 | Network & Wi-Fi hardening | Medium | Low | 10 | Website hardening | Medium | Medium | 11 | Asset & data inventory | Medium | Medium | 12 | Payment change verification | High | Low | 13 | Third-party access review | Medium | Low | 14 | Incident response plan | High | Low | 15 | Quarterly review | Medium | Low ## What to do if you suspect an attack - Do not panic and do not pay any ransom before getting advice. - Disconnect affected devices from the network (unplug or disable Wi-Fi) but do not switch them off — evidence in memory may help. - From a clean device, change passwords for affected accounts and revoke active sessions. - Call your IT partner and, if relevant, your bank and cyber insurer. - Check legal notification obligations if personal data may be affected, and document everything you do. ## Frequently asked questions Is antivirus enough for a small business?No. Endpoint protection is important, but most attacks start with stolen credentials or phishing. MFA, updates, backups and awareness matter at least as much. How much should a small business spend on cybersecurity?There is no universal figure. Many of the most effective controls in this checklist cost little beyond time. Start with the free and low-cost items, then invest based on the value of your data and the impact of downtime. Do we need cyber insurance?It can be valuable, but insurers increasingly require basics such as MFA, backups and patching before they will provide cover. Implementing this checklist helps with both security and insurability. How often should we train employees?Short sessions a few times a year work better than one long annual training. Add simulated phishing exercises if possible. ## Get a professional second look Working through this list yourself is a great start. If you would like an expert to check everything, explain the risks in plain language and fix the critical gaps for you, our Cybersecurity Audit & Hardening package covers all fifteen areas in two to three weeks. Ongoing protection is included in our Managed IT Support plans. --- # Cloud Migration for Small Businesses: A Step-by-Step Guide URL: https://sisusoft.com/cloud-migration-small-business-guide/ Published: 2026-03-26 For many small businesses the question is no longer whether to use the cloud — email, documents and accounting probably live there already — but what to do with the remaining server in the back office, the line-of-business application installed on it and the file share everyone maps as drive "S:". Moving those workloads can cut costs, improve security and make remote work painless. Done carelessly, it can also produce surprise bills and a very long weekend. This guide walks through the seven steps we use with clients to migrate predictably. It is written for business owners and office managers as much as for IT staff. ### Key takeaways - Start with an inventory: you cannot migrate what you have not listed, including the hidden dependencies. - Not everything should be "lifted and shifted" — many workloads are better replaced by SaaS or retired entirely. - Model monthly costs before you migrate, and set budgets and alerts on day one. - Security and backups must be designed in, not added after the move. - Rehearse the cut-over and always have a rollback plan. ## Why small businesses move to the cloud - Hardware end of life. A server bought years ago needs replacing, and buying new hardware for another five-year cycle feels like the wrong bet. - Remote and hybrid work. VPNs into an office server are slow and fragile; cloud services are designed for access from anywhere. - Resilience. A single server in a cupboard is a single point of failure for fire, theft, flood and ransomware. - Security. Major cloud providers invest heavily in physical and platform security, patching and monitoring. - Predictable operations. Less time spent on hardware, power, cooling and on-site maintenance. The cloud is not automatically cheaper, though. A server that runs 24/7 at full size in the cloud can cost more than the hardware it replaced. Savings come from choosing the right strategy for each workload, right-sizing, and switching off what you do not need. ## Step 1: Build a complete inventory List everything that runs on your current infrastructure, and for each item record who uses it, how critical it is, how much data it holds and what it depends on: - Servers (physical and virtual), their operating systems and age - Applications, including the database each one uses and its licence terms - File shares, their size and folder permissions - Network services: DNS, DHCP, VPN, printers, scanners that save to a folder - Scheduled jobs, scripts and integrations that nobody remembers until they stop - Backups: what is backed up, where, and when a restore was last tested Pay special attention to dependencies. The accounting software might rely on a specific database version, a scanner might write directly to a shared folder, and a reporting script might run every night on the server's scheduler. Each of these needs a plan. ## Step 2: Choose a strategy for each workload (the "6 Rs") | | Strategy | What it means | Good for | Rehost ("lift and shift") | Move the server as-is to a cloud virtual machine | Legacy apps that cannot change quickly | Replatform | Small changes to use managed services, e.g. a managed database | Apps where the database is the main burden | Refactor | Re-architect the application for the cloud | Strategic custom software with a long future | Repurchase | Replace with a SaaS product | File shares, email, CRM, HR, accounting | Retain | Keep on-premise for now | Hardware-bound systems, very low-latency needs | Retire | Switch it off | Unused or duplicate systems — more common than you think For a typical small office, the result is often: file shares move to SharePoint/OneDrive or Google Drive, the line-of-business application is rehosted or replaced with its vendor's cloud edition, and a few old services are retired. ## Step 3: Choose the platform AWS, Microsoft Azure and Google Cloud can all host small-business workloads reliably. The deciding factors are usually practical: - Existing ecosystem: if you already use Microsoft 365, Azure integrates naturally with your identities; Google Workspace users may prefer Google Cloud. - Application requirements: some vendors certify their software only on particular platforms. - Skills: pick the platform your support partner knows well. - Simplicity: for a single website or small app, a managed hosting provider may be simpler and cheaper than a hyperscaler. ## Step 4: Model the costs Use the providers' pricing calculators to estimate compute, storage, backup, data transfer and licensing. Then apply three savings levers: - Right-size: on-premise servers are usually over-provisioned. Start smaller and scale up if needed. - Schedule: development or batch servers do not need to run at night or at weekends. - Commit: for steady workloads, reserved instances or savings plans substantially reduce the price compared with on-demand rates. Compare the result with the full cost of staying put: hardware replacement spread over its lifetime, support contracts, power, backup media and the hours spent maintaining it. Set up budgets and cost alerts in the cloud console before you create the first resource. ## Step 5: Design security and backup from the start - Identity: single sign-on with your existing directory and multi-factor authentication for every account, especially administrators. - Least privilege: separate admin accounts, minimal permissions, no shared root credentials. - Network: no management ports (RDP, SSH) open to the internet; use a VPN, bastion or identity-aware access. - Encryption: at rest and in transit — usually a checkbox, but make sure it is ticked. - Logging: enable audit logs and alerts for unusual activity. - Backups: follow the 3-2-1-1-0 rule, including an immutable copy that ransomware cannot delete, and test restores. ## Step 6: Migrate in waves and rehearse the cut-over Start with something low-risk to learn the process — an archive file share or a test server. Then move workloads in waves, grouped by dependency. For each wave: - Copy data in advance and keep it synchronised. - Test the migrated system with real users before the cut-over. - Schedule the cut-over at a quiet time and communicate it clearly. - Perform the final sync, switch DNS or connections, and verify. - Keep the old system available read-only for a defined period as your rollback plan. ## Step 7: Optimise after the move The first month in the cloud is when you learn most. Review actual usage and costs, resize over-provisioned resources, delete orphaned disks and snapshots, apply reservations for steady workloads and automate routine tasks. For software teams this is also the moment to introduce continuous integration and deployment and infrastructure-as-code, so environments can be rebuilt reliably. ## Common mistakes to avoid - Migrating without an inventory and discovering a forgotten dependency on Monday morning. - Copying an oversized server one-to-one and paying for capacity you never use. - Leaving remote desktop open to the internet "just for the migration". - Assuming the cloud provider backs up your data — under the shared responsibility model, protecting your data is your job. - Forgetting licensing: some software licences do not allow cloud hosting or cost more there. - No owner for the monthly bill. ## Frequently asked questions How long does a small business cloud migration take?For an office with one or two servers and a file share, planning takes about two weeks and the migration itself is usually completed in one or two planned weekends. Will we have downtime?Usually only a short, scheduled window during the final cut-over, often outside business hours. Data is copied and synchronised in advance. Is the cloud secure enough for sensitive data?Major providers offer strong security, but configuration is your responsibility. With MFA, least privilege, encryption, logging and good backups, a cloud environment is typically far more secure than a server in an office cupboard. Can we move back if it does not work?Yes, if you plan for it. Keeping data in standard formats and documenting the setup avoids lock-in. ## Next steps A good migration starts with a good plan. Our fixed-price Cloud Assessment & Migration Plan delivers the inventory, strategy, cost model, security baseline and runbook described in this guide in two weeks. Or ask us a question — we are happy to give a quick opinion on whether the cloud makes sense for you. --- # 12 Everyday Business Problems Custom Software Can Solve URL: https://sisusoft.com/everyday-business-problems-custom-software-solves/ Published: 2026-03-04 Every business has them: small, persistent problems that nobody planned for and everybody works around. The spreadsheet that only one person understands. The order that gets typed into three systems. The report that takes a whole Friday to assemble. Individually they look harmless. Together they quietly consume hundreds of hours a year, introduce errors and make growth harder than it needs to be. Custom software is not always the answer — sometimes a configuration change or an off-the-shelf tool is better. But for a surprising number of everyday problems, a small, well-built piece of software makes the issue simply disappear. Here are twelve of the most common ones we see, how to recognise them and what the solution typically looks like. ### Key takeaways - Most "technology problems" in small businesses are really data problems: information lives in the wrong place or is entered more than once. - The best candidates for custom software are frequent, rule-based tasks that are specific to how you work. - Small internal tools often pay for themselves within months, without replacing your existing systems. - Start with one painful process, measure the time it costs, and solve that before thinking about a big platform. ## 1. The spreadsheet that runs the business The symptom: a critical spreadsheet — orders, stock, schedules, pricing — that has grown for years. It has hidden tabs, fragile formulas and one person who "knows how it works". Two people cannot edit it safely at the same time, and nobody is sure which version is current. The fix: a simple web application with a proper database, user accounts and permissions, an edit history and validation rules. Users keep a familiar table-like interface, but data cannot be accidentally overwritten and everyone sees the same truth. Importing the existing spreadsheet is usually the first step, so nothing is lost. ## 2. Typing the same data into several systems The symptom: a new customer is entered in the CRM, then the accounting software, then the project tool, then the newsletter platform. Each copy drifts out of date and typos multiply. The fix: an integration layer that treats one system as the source of truth and synchronises the others through their APIs. Often this does not even require a user interface — it is a small service running in the background. See our guide on business process automation for how to choose which flows to connect first. ## 3. Reports that take a day to build The symptom: every week or month somebody exports CSV files from several tools, pastes them into a workbook, fixes the formatting and emails a PDF. The report is late, manual and occasionally wrong. The fix: an automated pipeline that collects the data on a schedule and feeds a live dashboard. Managers see current numbers whenever they want, and the person who used to build the report gets their Friday back. ## 4. Leads that fall through the cracks The symptom: enquiries arrive by web form, email, phone and social media. Some get answered quickly, some wait days, some are never answered at all. Nobody knows the conversion rate. The fix: a single intake process that captures every lead in one place, assigns an owner, sets follow-up reminders and records the outcome. This can be built around an existing CRM or as a lightweight custom tool if your sales process is unusual. ## 5. Quotes that take too long The symptom: preparing a quote means looking up prices, calculating materials or hours, applying discounts and formatting a document. It takes an hour, and customers who wait go elsewhere. The fix: a quoting calculator that encodes your pricing rules, produces a professional PDF in seconds and stores every quote for follow-up. Rules change? Update them once, centrally, instead of in a dozen templates. ## 6. Scheduling chaos The symptom: appointments, field visits or shifts are managed with a shared calendar, a whiteboard and many phone calls. Double bookings happen, and last-minute changes are not communicated. The fix: a scheduling tool tailored to your constraints — skills, locations, equipment, travel time — with automatic confirmations and reminders by email or SMS. For many businesses, a configured booking platform is enough; custom software is worth it when your rules are complex. ## 7. "Where is my order?" calls The symptom: customers call or email to ask about status, and staff have to look it up in several places before answering. The fix: a customer portal or automatic status notifications triggered by real events in your system. Every avoided call is time saved on both sides, and customers trust a company that tells them what is happening before they ask. ## 8. Paper forms and manual approvals The symptom: purchase requests, holiday requests, inspection checklists or delivery notes still travel on paper or as email attachments. Approvals get stuck in inboxes. The fix: digital forms with built-in validation, routed automatically to the right approver, with mobile access and an audit trail. Field staff can complete checklists on a phone, even offline, with photos attached. ## 9. Inventory you cannot trust The symptom: the system says there are 40 units, the shelf says 12. Sales promise stock you do not have, or you over-order to be safe. The fix: barcode or QR scanning at every movement, integration with your sales channels, and alerts for low stock. Accurate inventory frees cash tied up in safety stock and prevents disappointed customers. ## 10. Onboarding and offboarding by memory The symptom: when someone joins, accounts and equipment are set up from memory and something is always forgotten. When someone leaves, their access is not always removed — a serious security risk. The fix: a checklist-driven workflow that creates accounts, assigns licences and requests equipment automatically, and reverses everything on departure. This connects naturally with the controls in our cybersecurity checklist. ## 11. Knowledge locked in people's heads The symptom: answers to common questions live in the heads of a few experienced employees, who are constantly interrupted. When they are on holiday, work slows down. The fix: a searchable internal knowledge base, often combined with an AI assistant that answers questions from your own documents. Our article on practical AI for small businesses explains when this works well and when it does not. ## 12. Customer self-service that does not exist The symptom: customers must email you to download an invoice, change an address, renew a subscription or book a repeat service. The fix: a secure self-service portal. It takes routine work off your team and gives customers the 24/7 convenience they expect from larger companies. ## How to decide what to fix first You probably recognised more than one problem. Do not try to solve them all at once. Instead, score each one on three questions: - Frequency: how often does it happen per week? - Cost: how many minutes does it take each time, and what does an error cost? - Specificity: is the process specific to your business, or is it something a standard tool already does well? Multiply frequency by time to get the hours lost per year. Problems that are frequent, time-consuming and specific to your business are the strongest candidates for custom software. Problems that are generic are usually better solved by buying a tool — our build vs buy framework helps you decide. | | Problem | Usually solved by | Typical effort | Double data entry | Integration / automation | Days to 2 weeks | Manual reporting | Data pipeline + dashboard | 1–3 weeks | Spreadsheet as database | Small web app | 3–8 weeks | Complex quoting or scheduling | Custom tool | 4–10 weeks | Customer self-service | Portal (custom or configured) | 6–12 weeks ## What a good first project looks like The most successful first projects are small and measurable. For example: "Reduce the time to produce a quote from 45 minutes to 5" or "Eliminate re-typing of web orders into accounting". They are delivered in weeks, not months, and they build confidence — and budget — for the next improvement. That is why we start custom work with a short, fixed-price Discovery & Blueprint: it turns a frustration into a costed plan you can act on, with or without us. ## Frequently asked questions Is custom software only for large companies?No. Modern frameworks and cloud hosting make small, focused applications affordable for businesses of any size. Many useful internal tools cost less than a year of the subscriptions they replace. Will custom software replace our existing tools?Usually not. Most projects connect and extend the tools you already use rather than replacing them, which keeps cost and disruption low. How do we avoid depending on one developer?Insist on code in a repository you own, documentation, automated tests and mainstream technologies. That way any competent team can take over. How long does a typical small tool take to build?Focused internal tools are often delivered in four to eight weeks, including design, testing and training. ## The bottom line Everyday problems deserve attention precisely because they are everyday: their cost compounds. Pick the one that annoys your team the most, measure it, and fix it properly. If you would like a second opinion on where to start, tell us about it — the first conversation is free. ---