Architectural signage fabricator and installer
Sales, art, production, permitting and installation handoffs were not connected, so project status, bottlenecks and billing stages were hard to see.
- Sales & CRM
- Operations & delivery
- Projects & PMO
Ready to scale your workflows?
AI use cases
Every use case comes from a real Fruition client engagement, with the client's name withheld. Select "See the build" for the process diagram, boards, automations and integrations.
Use case catalogue
Sales, art, production, permitting and installation handoffs were not connected, so project status, bottlenecks and billing stages were hard to see.
Long fabrication projects relied on manual pre-production checks that were often skipped, priorities were argued daily, requests got lost in chat, files were duplicated between systems and deliveries lacked proof.
A capital engineering team was constrained by an incumbent PPM tool: no self-serve dashboards, single-currency limits forcing manual conversions, manual entry of monthly actuals from the ERP, and poor visibility of team capacity.
A growing engineering and fabrication business had an over-complicated monday.com setup with dozens of automations on one board, manual handoffs from the CRM, paper QA forms and several overlapping form apps.
Sales, engineering, workshop and finance tracked jobs in separate spreadsheets and paper records, with duplicate data entry, quotes issued without enforced feasibility checks, and little visibility of rental asset usage or job status from sale to shipping.
A bespoke manufacturer planned production in detailed spreadsheets with some pen-and-paper steps, double-handled purchase orders into finance, and could not see true capacity to slot in urgent jobs or account for absences and machine downtime.
With no CRM, quotes were estimated in the ERP, retyped manually as Word letters and logged in a spreadsheet.
Staff printed job sheets from the point-of-sale system, retyped them into spreadsheets and annotated paper copies by hand, so complex and standard jobs collided in the same deadline weeks.
Sales tracking relied on manual spreadsheets, with customer data scattered and not connected to the order system, limiting reporting and forecasting.
Monday was used haphazardly across the business while multi-channel sales reporting was consolidated in spreadsheets and production, product development and customer support lacked structured workflows.
Quoting multi-component custom pieces, gating work before it reached the shop and comparing bid vs actual craftsman hours were all manual.
A 12+ person joinery workshop ran leads, production scheduling, installation dates and timesheets across spreadsheets, re-keying client details between sales and production.
Sales had little visibility of product development status and timeline changes, causing missed urgent requests and miscommunication across regional teams working in separate boards.
Product development across feasibility and development was tracked in spreadsheets with status communicated by email and meetings, and no central view of regulatory timelines or specialist workload.
A 25-person sales team managed around 2,000 active club accounts plus thousands of prospect clubs without a central CRM, making renewals, forecasting and rep activity hard to see.
Production and transport scheduling ran on multiple spreadsheets re-keyed from the ERP across several business units, causing manual effort, errors and poor visibility of job status on the factory floor.
Job scheduling, job details, safety forms, communication and timesheets were spread across spreadsheets and fragmented tools, creating manual overhead and coordination gaps between office and field staff.
A programme office ran projects in an online project-management tool that was being retired, needing a replacement with time and cost tracking, preserved historical rates and migrated project data before the cut-off.
A fragmented stack of disconnected website, subscription and CRM tools meant the B2B team relied on paper, email and spreadsheets, management lacked pipeline and customer visibility, and an inflexible club system was contributing to member churn.
Existing automations had broken, boards were disconnected and cluttered, and production scheduling was double-entered in a spreadsheet with no real-time view for the team.
Quoting ran in a separate CRM with duplicate quotes and manual uploads of equipment lists, the projects team did not use the CRM, and bids were sometimes missed, delaying projects and losing revenue.
Sales forecasting was run in a parallel spreadsheet alongside the quoting system, causing double entry and inconsistent figures, and existing boards lacked automation and role-specific views.
New product development projects (formulation, sampling, pre-production) lacked a standard process and visibility, with time lost in status meetings and unclear resource capacity.
A previous CRM had become costly and complicated, leaving the sales team without a simple way to manage leads, existing customers and visit activity.
Quoting the same project to several contractors inflated pipeline values, past quotes were hard to recall, and quote data was not linked to inventory for demand planning.
A new venture needed a single system for sales, project delivery and order fulfilment, including quote-to-cash with its accounting software, that could scale with growth.
Monday use was fragmented between the US and Israel teams with too many disconnected boards, the China team was not on the platform, and the sales pipeline was not connected to project delivery.
Jobs, time and quoting were tracked in spreadsheets and safety paperwork in Word/paper, making it hard to analyse job durations and capture labour accurately across multiple jobs per worker.
About 70 concurrent jobs were tracked in a basic plan without permissions or scheduling visibility, and quotes were produced by manually moving estimating exports into Word templates with no link to accounting.
Leads (30-40 a month) across three very different product lines were handled through spreadsheets and Outlook with no structured pipeline or reporting.
Project timelines, resourcing and budgets were maintained in a desktop scheduling tool plus multiple spreadsheets, with poor communication and no portfolio-wide view of resources or costs.
Strategy documents from global planning sessions had no local execution framework, leaders spent time chasing updates, and a static workspace could not report by both department and strategic pillar.
Projects, engineering and safety work ran in Smartsheet with separate task, ticketing, template and register setups, and the business wanted one enterprise platform rolled out across ten teams.
Large orders received a single production date and order details did not flow cleanly from the order form to production and delivery scheduling.
Staff had built their own monday.com boards without governance, creating silos, protective private boards and spending on unnecessary plugins.
Product launch projects relied on templates without linked dependencies or reliable reminders, so dates slipped and management lacked an at-a-glance view of overdue work.
Sales data on accounts, renewals and orders lacked a single structure and consistent terminology, limiting revenue forecasting visibility.
Partner leads and marketing requests were handled across HubSpot, email and Trello with a problematic HubSpot-monday integration, creating manual back-and-forth and poor partner visibility.
Lead handling, handoffs between sales, finance and planning, and production scheduling relied on manual updates and printed plans, with unclear task ownership and anyone able to edit critical fields.
Projects were tracked manually across several systems with Excel-based invoicing and cost tracking, scattered documentation, little real-time visibility and no mobile access for field teams.
The existing CRM offered poor reporting and dashboards, leaving little visibility of lead flow, quoting activity and sales performance, with leads keyed in manually.
Customer, sales and inventory information lived in separate systems with no CRM tying sales activity to stock and orders.
Customer and sales history lived in an ageing on-premise CRM that was costly to maintain and gave poor reporting, with years of communication records that needed to be retained.
R&D projects and multi-brand client orders were tracked in Excel, with no secure segregation of client data or cross-project reporting.
Custom engineering work was scheduled in a spreadsheet that could not assign engineers to line items, track time or holds, or provide capacity planning.
Graphics tasks sat in a basic planner tool and new product development was tracked in spreadsheets, with little automation or integration between systems.
With no CRM (a previous one had been abandoned), the pipeline lived in one multi-tab spreadsheet and the head of sales compiled a weekly summary by hand.
Industries
Tell us the process you want to fix. If it isn't here yet, it's likely our next build.
Pick a time and we'll map your pipeline live on the call: your stages, your handoffs, your reporting. No slides.