Question 1

We already have a website. Do we need a new one?

Accepted Answer

Often not. A site that loads fast, reads well on a phone and says the right things is rarely the bottleneck. What usually is: nothing happens after someone fills in the form. Connecting the existing site to your CRM and follow-up costs a fraction of a rebuild, so that is what we look at first.

Question 2

How long does a website take?

Accepted Answer

A focused marketing site runs 3–4 weeks. A site with full system integration — CRM routing, AI follow-up, automatic record creation — runs 6–8 weeks: a week of positioning and scope, two to three of design and content, two to three of build and integration, then a week for launch and handover. Scope is fixed in writing first, so the estimate is the one we're held to.

Question 3

Do you build on WordPress, Webflow, Shopify, or custom?

Accepted Answer

Whichever one your team can maintain without calling us. We build on all of them and earn nothing from any platform for recommending it, so the advice isn't shaped by our margin. The deciding question is who edits the site a year from now — if that is a non-technical person, it narrows the field faster than any feature comparison.

Question 4

What makes this different from hiring a web design agency?

Accepted Answer

Most agencies hand over a site and leave; what happens to an enquiry afterwards isn't their problem. We build the site and wire it into the systems behind it, so a lead is captured, qualified, routed, and followed up without anyone retyping it. If you only need a brochure site, a good local agency will serve you well.

Question 5

Will a new website bring in more business?

Accepted Answer

A website converts demand far more than it creates it, and that distinction decides whether it's the right thing to buy first. If people are already searching for what you do and not finding you, that's a visibility problem and a rebuild with proper technical SEO is exactly the fix. If nobody is searching yet, site work won't change that and demand generation should come first — we'll tell you which one you're in before you commit to a build. Either way: enquiries stop getting lost, first response stops depending on someone's inbox, and you can see which pages produce customers.

Question 6

What even is an AI agent — is it just a fancier chatbot?

Accepted Answer

No. A chatbot waits to be asked something and gives you an answer. An agent is given a goal and acts on it. A chatbot can tell you the status of an order; an agent watches your orders, spots the one that's slipped, emails the supplier, updates the CRM record, and flags your account manager — without anyone asking it to. The difference is judgment, and that's the part that gives your team their day back.

Question 7

Will it replace our staff?

Accepted Answer

Not the work that matters. Agents take the repetitive, rule-following layer — routing requests, updating records, chasing approvals, sending the fourth follow-up. That's the work that fills a day without needing a human brain. What's left is the work you actually hired people for: relationships, judgment calls, and the problems nobody wrote a process for. Most of our clients use this to grow without adding headcount, not to cut it.

Question 8

How long does it take to get one running?

Accepted Answer

A focused agent handling a single workflow takes 4–6 weeks from first conversation to live deployment. Agents that reach across several systems run 8–12 weeks. That breaks down as 1–2 weeks of discovery, 2–4 weeks of design and integration, 2–4 weeks of build and testing against real scenarios from your operation, and a final week of launch and handover. We scope it in writing first, so the timeline you're quoted is the timeline you get.

Question 9

Is our data safe? We can't have client information floating around.

Accepted Answer

We build agents that run inside your existing infrastructure wherever it's technically possible, and we don't route your operational data through any third-party platform you haven't explicitly approved. Where an external model is genuinely required, we tell you which one, what it sees, and what it retains — before you sign anything. Data handling, residency, and PIPEDA or GDPR obligations get addressed in writing in every engagement, not bolted on afterwards.

Question 10

What's a realistic first thing to automate?

Accepted Answer

The one that's costing you the most right now — which is usually not the one that feels most exciting. In discovery we map your highest-volume, highest-friction workflows and rank them by hours recovered against effort to build. In practice the first agent is often after-hours inquiry handling, lead follow-up, or status reporting. We start with one, measure what it actually saved, and expand from there. If the hours recovered don't cover the build, the honest recommendation is to leave that workflow manual.

Question 11

Do we really need a CRM, or can we keep using spreadsheets?

Accepted Answer

Spreadsheets hold up fine until they don't. The break point is usually when follow-ups, deal stages, call notes, and email threads stop fitting in one person's head — somewhere north of 30 active contacts, or the moment a second person needs the same view. The cost isn't the spreadsheet; it's the deals that quietly die because nobody remembered to follow up. If you're not there yet, a well-kept spreadsheet is still the right tool.

Question 12

Which CRM should we be on?

Accepted Answer

We're tool-agnostic and we don't take referral fees, so the honest answer is: whichever one fits how you already sell. We map your actual process first, then choose the platform that fits it — HubSpot, Salesforce, Zoho, or something industry-specific. If you're already on a platform that works, we'd rather automate it than migrate you. Switching CRMs is expensive and disruptive, and it's rarely the real fix.

Question 13

How does AI make a CRM better?

Accepted Answer

It removes the data entry that makes people avoid the CRM in the first place. Calls and emails get logged automatically, notes get summarized, leads that have gone quiet get surfaced before they're cold, and follow-up drafts land in your rep's queue ready to review. The point isn't the AI — it's that your team stops maintaining the CRM and the CRM starts working for them.

Question 14

What does a CRM implementation cost?

Accepted Answer

Platform licensing is the small part and it's paid to the vendor, not to us — most teams under ten people land in the low hundreds per month, and some tiers are free. The real cost is the implementation: process mapping, data migration, automation build, and training. That's what we quote, as a fixed written scope, before any work starts. A typical engagement runs 5–7 weeks. You'll know the number before you commit.

Question 15

Our team doesn't update the CRM consistently. How do we fix that?

Accepted Answer

This is the single most common thing we're called in for, and it's almost never a discipline problem — it's a friction problem. People skip the CRM because updating it costs more effort than skipping it. So we make the system update itself: emails and calls auto-log, agents write records from real interactions, and the fields nobody uses get deleted. When the CRM stops asking for manual work, adoption follows. Fixing the process is the job; the software is just where it lives.

Question 16

What exactly is a client portal, and why would our clients want one?

Accepted Answer

It's a private, secure space where your clients log in to see project status, review and approve documents, exchange files, settle invoices, and message you — instead of digging through an email chain to find the version you sent in March. Clients like it because they can answer their own question at 11pm without waiting on you. You like it because they stop asking.

Question 17

Will our clients actually use it, or just keep emailing us?

Accepted Answer

They use it when it's genuinely easier for them than email — which is a design problem, not a client problem. One-click approvals, a timeline they can read at a glance, and file upload that doesn't require a password reset every time. We design the portal around what your clients contact you about most, then route those specific requests through it. The email volume drops because the reason for the email is gone.

Question 18

Is this worth it if we only have a handful of clients?

Accepted Answer

Often yes. Even at five or ten clients you're re-sending the same documents, answering the same status questions, and chasing the same signatures. That overhead scales with how complex each engagement is, not just how many you have. It also changes how your business reads to a prospect comparing you against a larger competitor. That said, if your work is genuinely low-touch, a portal adds a login your clients never asked for.

Question 19

Can it handle contracts and invoices too, or is that separate?

Accepted Answer

Same portal. We wire e-signature, invoicing, and payment collection into the flow so a client can review a proposal, sign it, and pay a deposit in one sitting without printing anything or opening a second tool. Where you already use something for contracts or billing, we integrate with it rather than replacing it — the portal becomes the front door, not another system to maintain.

Question 20

How secure is it? Our clients share sensitive information with us.

Accepted Answer

Data is encrypted in transit and at rest, access is role-based so each client only ever sees their own records, and two-factor authentication is enabled by default rather than offered as an option. Access is revoked the moment an engagement ends. For context, this is a meaningful upgrade over the current alternative at most firms, which is sensitive PDFs sitting permanently in two mailboxes. We'll document the specific controls for your setup as part of the build.

Question 21

We already use email and a shared to-do list. Why do we need more?

Accepted Answer

Email and a to-do list work well for one person and start failing the moment delivery involves three. Nobody can see what's blocked, ownership is implied rather than assigned, and the status of a job lives in whoever last touched it. A real system gives everyone — you, your team, your subcontractors — one view of what's happening, by when, and whose call it is. Mostly it ends the "I thought you had that" conversation.

Question 22

Do we have to switch tools? Our team just learned this one.

Accepted Answer

Usually not. If you're already on Asana, Monday, ClickUp, Jira, or something else your team has adopted, our default is to build on it rather than move you. Migration burns weeks of goodwill and rarely fixes the underlying problem, which is normally missing structure rather than the wrong software. We only recommend a switch when the platform genuinely can't do what your delivery process requires, and we'll show you exactly where it falls down before suggesting it.

Question 23

How does AI fit into project management?

Accepted Answer

It handles the coordination work a project manager would otherwise do by hand: drafting the plan from a scoping document, flagging tasks drifting toward a missed date, summarizing a forty-comment thread into what was decided, and rebalancing work when someone is visibly overloaded. It won't make the judgment calls. It makes sure the judgment calls reach you while there's still time to make them.

Question 24

Our projects always run over. Can a system fix that?

Accepted Answer

A system on its own doesn't fix it — it just shows you the overrun sooner. That's most of the value. Deadlines are usually missed because a dependency slipped three weeks earlier and nobody noticed until the end. With real dependency tracking and automated alerts, that slip surfaces the week it happens, when it's still cheap to fix. The system gives you the warning. Acting on it is still your call.

Question 25

How long before the team is using it consistently?

Accepted Answer

Realistically 2–4 weeks to build the habit, on top of a 5–8 week build. The deciding factor is that every task goes into the system — the moment a parallel to-do list survives, adoption collapses. We roll out on your most active project rather than everything at once, so the team sees it working before it becomes mandatory. Onboarding is the difference between a system that gets used and one that gets abandoned, so we treat it as part of the build, not an afterthought.

Hand the busywork to AI.Keep your people onthe work that matters.

One system to bring prospects in, four to handle what happens next

Web Design

AI Agents

CRM

Client Portal

Project Management

Written scope, tested against your scenarios, owned by your team

Industries

Credentials

ERP and SAP

Eight stages, one machine

Attract

Engage

Qualify

Book

Nurture

Convert

Review

Grow

15 years of ERP and SAP, before DesignareLux

Manufacturing

Telecommunications

Residential Services

Not sure where to start?

What clients report after handover

Questions we get before every engagement