The starting point
Work spread across tools.
Customer and project information lived in spreadsheets, inboxes and a growing collection of automations.
CRM customisationTwenty
Twenty CRM customisation & AI
We configure Twenty around your customers, sales and operations, then build the working screens, connections and AI your team needs. A tailored CRM, from setup to adoption.
What we build
New enquiries. Live projects. Orders to fulfil. Relationships to look after. We shape the records, working screens, connections and AI around how your team handles that work.
Twenty provides the foundation. LogicFox designs and builds your implementation.
A bespoke implementation, with clear ownership, human review and ongoing care agreed in scope.

“Could we talk about bringing our customer project updates into one workspace?”
Follow-up ownerUnassigned
“The brand system and launch files are approved.”
StageAwaiting approval
“I still need to confirm the access contact and any building restrictions.”
VisitNot confirmed
“Two sites, one agreement—and a service note still to file.”
Account reviewTo scheduleApproval received.
Handover waiting.
Morgan has approved the launch files. The project still says Awaiting approval.
Sample records and prepared AI suggestions. Changes stay here; nothing is sent.
Scene3D / Customer implementation
Scene3D creates 3D visualisations and virtual tours. We helped bring the business behind that work into a shared Twenty CRM and connected workflows.

“Working with LogicFox was a game changer. They automated our processes, streamlined our CRM, and boosted our team's productivity in no time.”
The starting point
Customer and project information lived in spreadsheets, inboxes and a growing collection of automations.
What we implemented
A shared Twenty CRM, an opportunity pipeline and connected workflows for intake and follow-up.
What the team can see
Connected customer and project history, alongside a visible renewal book and billing review.
What we can build
A sales pipeline. Your team’s working desk. A useful customer portal. We shape the records and the experience around the people using them.
Across the working day
Alder customer workspace
“Could we talk about bringing our customer project updates into one workspace? We would like to understand what is possible before agreeing the scope or timing.”
Clarify the customer-workspace scope and timing.
Native configuration
Example project fields
The working screens shown here are custom design possibilities. Integrations, customer access and AI are designed and developed to the agreed scope.
Custom working views, designed around Twenty’s connected records.
See the customer experienceShowing team workspace. Alder customer workspace.An experience for your customers
Your team has the full working picture. Customers get a project space shaped around them, with your identity and a clear view of what comes next.

The customer’s sideTheir project, in their own time.
Your launch,
coming together.
Morgan has approved the launch files. A short walkthrough is the next conversation.
One set of records. Two experiences.
A customer portal is bespoke LogicFox development connected to Twenty, not a standard Twenty feature. Sign-in, access and what is shared are designed and agreed for each implementation.
These are possibilities to shape together, rather than a fixed bundle in every build.
Customers, contacts, opportunities and follow-up in a pipeline shaped around your sales process.
Projects, files, approvals and responsibilities together in a working view for your team.
Sites, agreements, service history and renewal preparation connected to the customer.
A bespoke portal for the project information, documents and requests you choose to share.
Views of open work, ownership and outstanding information, drawn from the same records.
Source-linked answers, preparation and drafts, with proposed changes shown for review.
Different records. Different work.
Explore a different working setup, or shape a starting point around what you manage.
Projects, deliverables and a clear customer handover.
Sites, agreements and the next account review.
Roles, interviews and feedback to coordinate.
Choose your records and the work you want to improve.
Explore the records, sources and proposed changes.
Work with the tools you already use
Bring correspondence, customer records and the next action into the same working picture. Your team can see what has been asked, what is known and who needs to take it forward.

Riley MorganHarbour Group
“Could we arrange site photography at Linden Court?”
“I still need to confirm the access contact and any building restrictions.”
Linden Court
Harbour GroupRiley Morgan · Portfolio manager
Confirm Linden Court’s access contact and visit requirements
The customer’s email gives the team a useful starting point: a photography visit, with access information still to collect.
Preparation can move forward; the visit stays unconfirmed.
See relevant correspondence and scheduled activity beside the customer and work it concerns.
Connect the people, sites, projects and responsibilities your team needs to keep in view.
Bring an agreed billing status into the work. Your accounting system continues to handle invoices and payments.
We choose and build connections around your systems, their access and the actions you want to permit.
AI with a useful place in the work
Ask about a customer. Bring the details together before a visit. Draft the next conversation. An assistant can turn agreed sources into something your team can use.
Account answer
What’s happening with Alder?
There is current delivery work and a separate opportunity to explore.
Morgan has approved the launch files. The team still needs to arrange the handover walkthrough.
CRM stage: Awaiting approval — approval received; stage update still to review. Project lead: Jamie EllisAlder wants to explore bringing customer project updates together. Scope, timing and price are still to discuss.
Follow-up owner: UnassignedAsk which updates customers need, which tools Alder uses today and what timing they have in mind.
Sources behind this output
Your implementation defines the assistant’s sources, permissions and review steps.
Showing ask about an account.
Implementation and adoption
We bring the model, the working experience and the team together. Each stage leaves you with something concrete.
to the next
customer chapter.
Customers, opportunities,
projects and relationships.
Useful screens, connected tools
and defined AI responsibilities.
A team ready to use it.
Clear responsibility for its care.
Walk through the people, records and tools involved. Find the awkward joins and choose a useful first release.
You receiveA workflow map, priorities and a shared definition of success.
Make the records and working screens tangible. Review the proposed experience and AI assistance with the people who will use them.
You receiveA connected data model and a clickable prototype to review.
Configure Twenty, develop the agreed custom work and connect the tools. Test sample imports, access and what should happen when information is missing.
You receiveThe agreed system, tested connections and a switch-over plan.
Train the team around its actual work. Set up administrative access and make responsibility for operating and improving the system clear.
You receiveTeam training, documentation and an agreed plan for ongoing care.
We assess the data you already have, map its fields and relationships, and test a sample import before the switch. We agree which history, files, cleanup and checks belong in the migration scope; not every feature of an old system transfers automatically.
We agree whether the system is client-operated or managed, who holds the accounts and administrative access, and who handles backups, recovery and upgrades. Commissioned work follows the contract; Twenty and other software keep their own licences.
The implementation timetable follows the agreed scope. Hosted and self-hosted arrangements, platform features, connected tools, AI usage and ongoing care each need an agreed owner and budget.
How we workInvestment
Focused work is quoted to the change involved. For broader implementations, these ranges help set an initial expectation. We confirm the scope and timetable with your quote.
Core records, a defined pipeline, agreed data import and team handover. Data quality, permissions and migration scope are agreed before a fixed quote.
Related workflows, approved integrations and prepared work for people to review. API access, source data and each write permission are agreed in scope.
Complex processes, specialist interfaces or a wider AI capability need their own discovery and quote.
Hosting, platform licences, connected services, AI usage and optional care are separately agreed. These are planning guides, not fixed feature bundles.
Not ready to define the whole build?
The optional £150 Blueprint & Prototype makes one priority workflow tangible before an implementation commitment.See what the Blueprint includesA few useful answers
Twenty is the CRM foundation. LogicFox shapes the data model, configuration, integrations, custom working interfaces and useful AI around the engagement. The interactive screens are fictional examples of the custom work we could design, rather than a promise that every element is a standard Twenty screen.
Records and field types, relationships, pipelines, role-specific views, workflows, applications and connected tools. Some changes are native Twenty configuration; others need custom development or a connected service. We check the installed version, edition, access and scope before committing to the build.
Yes, migration can be included in the implementation. We first assess the source, relationships, data quality, access, history and attachments. We then agree the mapping, cleanup, sample imports and switch-over plan. An import is not assumed to preserve every source-system feature.
For a self-hosted arrangement, the agreed installation and accounts can sit under your control. We document the custom work, configuration, access, backup and recovery arrangements, and the person responsible for operating it. Platform and dependency licences still apply. Client-operated and managed arrangements have different responsibilities and are agreed explicitly.
That is a design and permissions decision, not a default promise. Read-and-prepare assistance, human-reviewed changes and bounded automation have different risks and operating needs. We agree the sources, permitted actions, exceptions and monitoring for each workflow. The demonstrations here only update their local fictional records.
Your quote sets out the records, screens, integrations, migration and adoption included, together with the assumptions and access needed to deliver them. A focused first release can be scoped around one priority. Hosting, licences, connected services, AI usage and optional care are separately agreed, so you can assess both the build and its ongoing operation.
Start with a conversation
Tell us what your team manages, where the process gets awkward and which tools you already use. We’ll talk through fit and a sensible next step.
Book a free consultationA free 30-minute conversation.Or tell us about your projectAn optional, tangible starting point
A workflow and data model, a clickable prototype using example data, and a phased implementation plan with a fixed quote for the agreed build.
One agreed priority workflow and its supporting records, with one consolidated revision.
Explore the £150 BlueprintWithin five UK working days after payment, scope and required inputs are confirmed. Carlo confirms your actual delivery date.
£150 credited against an implementation build started within 60 days of blueprint delivery. The credit is not a cash refund.
Full refund before work starts or if your request falls outside this offer. After work starts, we address issues through the agreed deliverables and included revision, subject to your applicable rights.
Full scope, delivery and refund terms