Frequently Asked Questions

Business Central is Microsoft's ERP (enterprise resource planning) system for small and mid-sized businesses. It runs your general ledger, accounts payable and receivable, inventory, purchasing, and orders in one cloud system, so the numbers your business runs on live in one place instead of five.

Licensing is per named user, per month, on an annual commitment. Full users sit on one of two tiers: Essentials covers finance, sales, purchasing, inventory, and projects, and Premium adds service management and manufacturing. You choose one tier for the whole company rather than mixing them. Team Members is a cheaper license for people who only look things up or approve. Add-on apps and Copilot Credits for the AI agents are billed separately. Microsoft publishes current rates on the Business Central pricing page.

QuickBooks records what happened; Business Central runs the operation. Once you need inventory that reconciles, approval workflows, multiple entities, or a month-end close that holds up, QuickBooks needs a web of spreadsheets and add-ons around it. Business Central replaces the web, and it scales without replatforming. We wrote a fuller guide on when to graduate off QuickBooks Online.

You have roughly 10 to 200 people, you have outgrown QuickBooks or an aging system like Great Plains or Inflow, and inventory, traceability, or a reliable close matter to your business. Distributors, light manufacturers, and product companies are the classic fit. On the other side: if QuickBooks still fits how you operate, keep it, and if you need enterprise-scale multi-entity master data management, Business Central has a ceiling and the answer may be a bigger platform. Weighing platforms? See our Business Central versus NetSuite comparison.

Dynamics 365 Sales is Microsoft's CRM (customer relationship management) system. It tracks accounts, contacts, deals, and follow-ups in one shared pipeline, inside the Microsoft tools your team already uses, so selling stops depending on one person's memory.

Licensing is per user, per month, on an annual commitment, and you license only the people who work deals, not the whole company. Three tiers step up in capability: Professional for straightforward pipeline management, Enterprise for deeper customization and forecasting, and Premium for the AI-assisted selling features. Copilot Credits are billed separately from the seat licenses. Microsoft publishes current rates on the Dynamics 365 Sales pricing page.

Against a spreadsheet, the difference is that nothing falls through: every deal has an owner, a stage, and a next step. Against big-name CRMs, the difference is fit and cost: you get enterprise-grade pipeline management that plugs into Outlook, Teams, and your ERP without a second ecosystem to maintain.

A sales team of two to twenty that quotes deals, hands work to delivery, and needs leadership to see the pipeline without asking. It is strongest connected to Business Central, so won deals flow straight to fulfillment and invoicing. A business with a handful of repeat customers and no live pipeline does not need a CRM; a shared spreadsheet does the job. And if the team will not agree to live in the system, the software cannot fix that. On the boundary between CRM and ERP: should sales enter orders in the CRM or the ERP?

Project Operations is Microsoft's system for businesses that sell projects. Quoting, staffing, time tracking, and billing live in one flow, so a project's real margin is visible while you can still do something about it.

Licensing is per user, per month, on an annual commitment, covering the people who quote, staff, track time against, and bill projects. There is one full-user plan rather than a tier ladder, so the sizing question is who genuinely works in the system: usually project managers, resourcing, and finance, rather than everyone who touches a project. Copilot Credits for the prebuilt time, expense, and approval agents are billed separately. Microsoft publishes current rates on the Project Operations pricing page.

Most project businesses run a quoting spreadsheet, a project tool, a timesheet app, and an invoicing system that never quite agree. Project Operations replaces the handoffs between them, which is exactly where hours go unbilled and margin leaks.

Services firms that live and die by utilization and project margin: engineering, consulting, field services, agencies. It is especially strong when projects run through Business Central for accounting. If your projects are short, uniform, and priced flat, a lighter project tool is cheaper and faster to run; this platform earns its keep when projects are big enough to leak.

Dynamics 365 Customer Service is case management for support teams. Every customer issue becomes a tracked case with an owner, a queue, and a history, so support stops living in a shared inbox.

Licensing is per service representative, per month, on an annual commitment, so it scales with the size of your support team rather than your headcount. Three tiers step up: Professional for case management, Enterprise for deeper automation and AI, and Premium for a combined contact center and CRM. Voice and digital channels come through Dynamics 365 Contact Center, which is licensed on its own. Copilot Credits are billed separately. Microsoft publishes current rates on the Dynamics 365 Customer Service pricing page.

A shared inbox tells you nothing about volume, response times, or repeat issues, and things silently fall through. Against helpdesk tools like Zendesk, the difference is the Microsoft connection: cases sit next to the customer's orders and history instead of in a separate silo. We explain the moving parts in Dynamics 365 Customer Service, explained.

Teams handling steady support volume, warranty or repair flows, or anything where 'did we ever respond?' is a real question, especially when case history should connect to orders and invoices. If you get a handful of support emails a week, a disciplined inbox is fine; case management pays off at volume, and it takes process discipline to run.

Power BI is Microsoft's reporting and dashboard platform, and Fabric is the data plumbing underneath it. Together they read live from your ERP, CRM, and other systems, and turn the numbers into dashboards leadership can act on. For a concrete picture, see your first Power BI report off Business Central data.

There are two models, and most companies end up using both. Per-user licensing covers the people who build and share reports: a Pro license for standard publishing, or Premium Per User for larger models and more frequent refreshes. Capacity licensing covers Microsoft Fabric itself, billed by the size of the capacity you run, either hourly with the ability to pause it, or on a one-year reservation. Above a certain capacity size, report readers stop needing individual licenses, which is the point where capacity costs less than seats. Microsoft publishes current rates on the Power BI and Fabric pricing page.

The Excel report you email around is a snapshot somebody had to build, and it is stale by the time it is read. Power BI reads the live systems on a schedule, applies the logic once, and everyone sees the same current numbers with security trimming what each person sees.

Leadership teams who ask the same questions every week (margin, cash, pipeline, utilization) and are tired of waiting for someone to compile the answer, especially on top of Business Central. One caution: if the underlying data is a mess, dashboards just make the mess visible faster. Sometimes the right first step is fixing the system of record, and discovery shows which situation you are in.

Business Central covers finance, inventory, and operations out of the box. Industry-specific needs, like catch weight for food distribution, FDA-compliant electronic signatures, or distributor EDI, are covered by vetted add-on products built for Business Central. We name them during design, quote their licensing before you sign anything, and remain your single point of contact. You never call Microsoft or the add-on vendor.

Usually no, and it is one of the most expensive line items you can buy. Most clients go live with opening balances and open transactions, and keep a snapshot of the old database for lookups. If a regulator or your business genuinely requires full history, we scope it eyes-open.

No. Business Central and Dynamics 365 do not care where your email lives, and switching to Microsoft 365 is never a requirement of the project. If you ever want that migration, it is a separate conversation.

Maybe. If QuickBooks still fits how you operate, staying on it is the right call. The move makes sense when the workarounds become the system: accounting in spreadsheets, inventory counts nobody trusts, and a close that never quite closes.

Managed IT means we operate your entire IT function for a flat monthly fee: helpdesk for your staff, patching, backups, security, vendor management, and a documented plan. It is the IT department you would hire, without hiring one.

Break-fix support (call a tech when something breaks, pay by the hour) is reactive by design. Managed IT is a flat monthly fee for keeping everything running, so prevention, monitoring, documentation, and planning are part of the service rather than billable extras.

Companies of roughly 10 to 75 people with no internal IT, where technology problems land on an office manager or the owner. It is also the right answer when insurance, clients, or auditors start asking questions your current setup cannot answer. If you already have a capable internal IT team, co-managed IT is usually the better structure, and if the deciding factor is the lowest per-seat price, flat-fee senior coverage is rarely the lowest bid.

Co-managed IT puts our bench behind your internal IT person. They stay in charge and stay first line; we bring the escalation depth, the tooling, vacation coverage, and a second set of eyes on security.

Hiring a second IT person costs a salary and still gives you two single points of failure. Co-managed gives your one person a whole team's depth for a fraction of that, without taking their job or their authority.

One-person IT departments at growing companies: the person is good, but they are stretched, they cannot take a real vacation, and some problems are simply bigger than one person. Much of the tooling is already in the Business Premium licensing you own. If nobody internal owns IT at all, there is nothing to co-manage, and fully managed IT fits better. The model also depends on the internal person seeing a bench rather than a threat, so we set that up clearly from the start.

Microsoft 365 is the platform your business probably already runs on: Outlook email, Word and Excel, Teams, OneDrive and SharePoint files, and, underneath it all, the identity system that controls who can get into everything. Our service is setting it up properly, securing it, and running it. For what a proper setup involves, see the Business Premium setup checklist.

Licensing is per user, per month. Business Basic, Business Standard, and Business Premium run up to 300 users, and above that the enterprise plans take over. The tiers differ in what comes with them: Basic is web and mobile Office with email, Standard adds the desktop apps, and Premium adds the device management and security tooling that most of our work builds on. An annual commitment costs less per seat than a monthly one, which trades some flexibility for a lower rate. You can mix plans across the company within the seat limits. Microsoft publishes current rates on the Microsoft 365 for business comparison page.

Compared to Google Workspace, it is deeper on desktop Office, device management, and security controls, and it is the default in regulated and professional industries. Compared to an aging on-premises Exchange server, the cloud service removes the hardware, the patching, and the single point of failure.

Any business that lives in email and files, and especially any business whose tenant settings have accumulated by accident over the years; most of our security work starts with straightening out a Microsoft 365 tenant. If your company runs well on Google Workspace and has no Microsoft-specific needs, staying put is reasonable. We administer both.

Azure is Microsoft's cloud: the servers, databases, and networks your systems run on, rented by the month instead of bought by the rack. Our service designs, migrates, and runs it, sized to what you use.

Azure is not licensed per user. You pay for what each resource consumes: compute by the hour it runs, storage by the gigabyte held, and data by what moves out. The bill is a function of what you deploy, which is why sizing happens during design rather than as an up-front quote. Steady workloads get cheaper with reservations or a savings plan, committing to a one-year or three-year term, and Azure Hybrid Benefit lets you reuse Windows Server and SQL Server licenses you already own. Microsoft's pricing overview and pricing calculator let you model a specific design.

The server in your closet has to be bought for its busiest day, maintained, backed up, and eventually replaced, and it fails without a spare. Azure workloads scale with you, get patched and monitored as a service, and are backed by data centers with better physical security than any office closet.

It makes sense when you have an aging on-premises server, a line-of-business app that needs to be reachable from anywhere, or disaster-recovery requirements you cannot meet with hardware. Not everything belongs in the cloud, though: a stable workload with flat usage can be cheaper on owned hardware, and that math gets done before anything moves.

Security Operations is the always-on layer: monitoring across identity, email, and endpoints, with a human response when something looks wrong. A suspicious sign-in at 2am gets caught, investigated, and shut down, whether or not anyone at your company is awake.

Antivirus waits for a known-bad file. Modern attacks come through sign-ins, mailbox rules, and stolen credentials, which antivirus never sees. Security operations watches behavior across the whole environment, and pairs detection with someone who acts on it. Two of the foundations are covered in conditional access starter policies and setting up SPF, DKIM, and DMARC.

When clients trust you with sensitive data (legal, healthcare, finance-adjacent), when you are pursuing cyber insurance, or after a scare. It is not a substitute for the basics: if MFA is off and backups do not exist, we fix that first, because monitoring works best on an environment with the fundamentals in place.

Only if it is rolled out carelessly. AI tools surface whatever the signed-in person can already access, so oversharing that was invisible in file shares becomes very visible in answers. We fix permissions and governance first, then turn on AI, in that order.

No. The two platforms run in coexistence during the waves, so mail keeps flowing the whole time. Each mailbox cuts over at a scheduled moment, typically overnight or over a weekend, and the next morning that person opens Outlook to find their mail, calendar, and contacts waiting. The pilot wave exists to catch anything that would make that morning bumpy.

Mail, calendars, and contacts move to Exchange Online. Shared drives and My Drive content move into SharePoint and OneDrive, restructured with governance and permissions rebuilt deliberately rather than copied over. We keep the Google tenant in read-only mode for a defined window after cutover as a safety net, then retire it so you stop paying for two platforms.

A company of 10 to 75 people typically lands inside a quarter. The pacing driver is usually people rather than data volume: waves are sized so each group gets real attention on its cutover morning. Larger environments run the same structure with more waves; our largest moved 550 mailboxes and 6.5 TB of files.

Yes. We implement Teams Phone as part of the migration or as its own project: existing numbers ported, auto attendants and call queues configured, and desk phones, headsets, or softphone setups matched to each role. Number porting has lead time measured in weeks, so we file the paperwork early and keep the old system running until the port completes. Calls then live in the same platform as chat and meetings.

Copilot is Microsoft's AI assistant built into Word, Excel, Outlook, and Teams, working with your company's own data. Azure AI Foundry is the platform behind it for building custom AI on your data. Our service rolls both out with the governance to make them safe.

Microsoft 365 Copilot is licensed per user, per month, on top of a qualifying Microsoft 365 plan, so it is an add-on rather than a replacement. You license only the people who get it, which is why most rollouts start with one or two departments and widen once the time savings show up. Azure AI Foundry is consumption-based instead: there is no seat license, and custom AI is billed on the tokens and services it uses. Microsoft publishes Copilot rates on the Microsoft 365 Copilot for business page and Foundry rates on the Foundry pricing page.

Consumer chatbots run outside your company: they cannot see your business context, and anything pasted into them leaves your control. Copilot works inside your tenant, respects your permissions, and leaves your data where it lives. The difference is not the AI, it is the guardrails around your data.

When the team is drowning in drafting, summarizing, and searching its own documents, and leadership wants AI adoption to be deliberate instead of fifty employees quietly pasting company data into free tools. Readiness has one prerequisite: if file permissions are a mess, Copilot will surface documents people should never have seen, so governance comes first. Here is why SharePoint cleanup comes before Copilot, and our Copilot prompt playbook shows what day-to-day use looks like.

This is AI built around your specific bottleneck: document intake, classification, drafting, data extraction, the handoffs between systems that eat hours every week. We scope one painful process and rebuild it as software. One common shape: a document-extraction pipeline built on Azure AI Document Intelligence.

Off-the-shelf AI tools are generic by design; your bottleneck usually is not. Compared to hiring developers, you get a senior team that has built these systems before, for the duration of the build, without adding permanent headcount.

Good candidates are high-volume, rules-describable, and painful: hundreds of documents a week, a re-keying step everyone hates, an intake queue that eats a person. If you can describe the rules, the work can usually be automated. One-off tasks, judgment calls, and processes that change every month automate badly, and if the volume will not repay the build, the ballpark stage will show it.

Power Apps is Microsoft's low-code app platform. It turns the tracking spreadsheet everyone fights over, or the paper form somebody re-types, into a real app with structure, permissions, and an audit trail, built in weeks instead of quarters.

Your Microsoft 365 licenses already include limited Power Apps use, enough for simple apps built on standard connectors. The moment an app uses Dataverse or a premium connector, which most real internal apps do, it needs a Power Apps license: a per-user subscription for people who use apps regularly, or pay-as-you-go billed through an Azure subscription for seasonal and occasional use. Dataverse storage beyond what your licenses include is a capacity add-on. Microsoft publishes current rates on the Power Apps pricing page.

Traditional custom development is a much larger investment and a long-term maintenance commitment. The spreadsheet costs nothing until it silently breaks. Power Apps sits between: real software, built fast on the platform you already license, connected to the data you already have.

Build the internal process everyone works around: equipment checkouts, inspections, approvals, intake forms, job tracking. If the words 'the spreadsheet' come with an eye-roll, it is a candidate. Customer-facing products with heavy design needs, or complex custom logic at large scale, deserve traditional development; Power Apps is for internal operations, and it is excellent at exactly that.

Power Automate is the plumbing between your systems. When something happens in one place (a form submitted, an invoice approved, a file dropped), it makes the right things happen everywhere else, with no human re-keying in the middle. A typical starter project: a flow that auto-files incoming documents to SharePoint.

Basic flows on standard connectors are included with your Microsoft 365 licenses. Beyond that, licensing splits by what the automation is: a per-user subscription for flows a person runs, or a per-process license for automation that runs on its own schedule for the whole company. The per-process model is usually the cheaper answer for back-office work, because one license covers a flow no matter how many people it touches. Unattended desktop automation and process mining are separate add-ons. Microsoft publishes current rates on the Power Automate pricing page.

Tools like Zapier do something similar for consumer apps; Power Automate is the version that lives inside your Microsoft tenant, respects your security, and talks natively to Microsoft 365, Dynamics, and SharePoint without shipping your data through a third party.

Any recurring 'someone copies this from here to there' step: invoice routing, approval chains, onboarding checklists, notifications. The best candidates are boring, frequent, and precisely defined. Fragile processes that change weekly, and one-time migrations, are poor fits, because automation pays for itself through repetition.

Part 11 is the FDA's rule for electronic records and signatures. If a digital record replaces paper in a regulated process, the system has to prove who did what and when, enforce sign-offs, and prevent silent changes. We build those controls into the Microsoft systems you run.

The traditional answer is staying on paper binders, or buying a monolithic validated suite. We take a third path: implement the controls on the platform you already license, with validation support, so compliance stops being a separate system to buy and babysit.

It applies to life-sciences companies replacing paper records in regulated processes: pre-launch pharma, medical devices, labs. It gets urgent when production is scaling and the next FDA interaction is a matter of when, not if. Timing matters in the other direction too: if your processes still change weekly, locking them into validated systems too early creates churn. Stabilize the process, then validate it.

CMMC (Cybersecurity Maturity Model Certification) is the Department of Defense's cybersecurity certification for its supply chain. If your contracts touch controlled unclassified information, certification is becoming a condition of keeping and winning that work. We build the controls and get you assessment-ready. One scoping strategy that saves small suppliers real money: walling off your CUI instead of moving the whole company.

For years, defense contractors self-attested to NIST 800-171 and nothing was checked. CMMC ends that: a third-party assessor verifies the controls. The difference between self-attestation and certification is the difference between saying and proving.

It applies to defense contractors and subcontractors with controlled unclassified information in scope, and the clauses are already showing up in contracts and flow-downs. If you hold no controlled information and never will, basic cyber hygiene may be all your contracts require. Scoping is the first conversation, and it sometimes shrinks the problem dramatically. One strategy that saves small suppliers real money: walling off your CUI instead of moving the whole company.

HIPAA sets federal privacy and security rules for protected health information. It covers providers and every business associate that touches patient data, and it requires you to prove your safeguards, not just have them. We build and document those safeguards on your Microsoft stack.

The common substitute is 'we signed a BAA and we use encrypted email,' which covers a fraction of the Security Rule. Real compliance is access controls, audit logs, risk analysis, and evidence, which is a program, not a signature.

It applies to healthcare and healthcare-adjacent organizations that store or handle patient information: practices, billing companies, benefits firms, health-tech vendors selling to covered entities. If you never touch PHI, you need good security but not HIPAA scaffolding, and a short scoping conversation settles which world you are in. If your staff are already experimenting with AI, read why governed Copilot beats banning AI in a HIPAA-regulated org.

SOC 2 is an independent audit of how your company safeguards customer data. The output is a report your customers' security teams accept in place of endless questionnaires. We build the controls and keep the evidence current so the audit confirms rather than surprises.

The alternative is answering every enterprise customer's 300-question security review by hand, forever. One SOC 2 report replaces most of that, and the controls behind it make you genuinely more secure rather than just better at paperwork.

When you sell to bigger customers who hold you to their security standards, especially as a software or services business handling client data. The trigger is usually a deal: a prospect asks for the report you do not have yet. If your customers never ask for it and never will, the audit adds cost without opening any doors; get the underlying security right and add the report when the market asks for it.

No. Auditors and assessors have to stay independent, so the same firm cannot build your controls and certify the result. We build the controls, assemble the evidence, and sit beside you during the assessment, so the auditor finds a running system rather than a scramble.