Velmanta Case Studies

OMEGA DRUK: from enquiry to production in one process

Written by Radoslaw Strzelecki | Nov 17, 2026, 10:36:20 AM
CASE STUDY / OMEGA DRUK

How we connected customer service, quoting and marketing at a printing company, supporting 6 active HubSpot users and how the same model can support office teams in other manufacturing businesses.

The process in actionHubSpot × Velmanta
Enquiry→Quote→Order
System view · illustrative data and amounts
IndustryMade-to-order manufacturingPrinting · puzzles, games, packaging
Active HubSpot users6 peopleService, marketing, management and operations
ScopeService/Sales + marketingShared customer context in CRM
A similar implementationUp to 10 peopleIn an office team supported by HubSpot
Client / OMEGA DRUK
OMEGA DRUK Sp. z o.o.
Made-to-order production · printing
Client testimonial

“Velmanta helped us organise customer service and improve our team's day-to-day work. We have a clearer view of enquiries and orders, making it easier to coordinate our activities.”

Krzysztof PawlakPresident of the Management Board · OMEGA DRUK Sp. z o.o.

Project at a glance

OMEGA DRUK needed a shared view of enquiries scattered across email inboxes. Velmanta structured qualification, ownership and customer handling in HubSpot, connected won tickets to an order register and configured lead-quality signals for advertising platforms. The team gained clearer visibility into its work, potential project value and orders handed over to production.

01 / Business context

Every order is different.
One shared service process.

OMEGA DRUK Sp. z o.o. is a printing company delivering bespoke projects: puzzles, games, packaging and other custom products. Enquiries vary in quantity, specification, deadline and value.

Before preparing a quote, the team needs to check whether a project meets production requirements, including the minimum order quantity. Qualified enquiries can then move on to quoting.

6 active HubSpot users

Six people actively use HubSpot across customer service, marketing, management and operations. The company also has a production team. The implementation structures the office team’s work and makes enquiries and orders easier to coordinate.

3 customer service1 marketing1 company president1 operations

Implementation goal: structure the journey from first contact to production order, prioritise enquiries and connect lead quality with marketing activity.

Business goals

  • One shared enquiry queue with clear responsibility for customer handling.
  • Priorities based on project value, customer potential and timing.
  • Visibility into order value against planned production dates.
  • A connection between marketing activity and the quality of acquired leads.
02 / The challenge

An email inbox
cannot show the whole process.

Email held the customer conversations, while coordinating the work remained difficult. The team needed to see who owned each enquiry, what was pending and which request needed attention first.

Before implementation: Enquiries spread across shared and individual inboxes.

After implementation: One shared ticket queue for connected channels.

Before implementation: Emails alone made status and ownership difficult to track.

After implementation: Defined process stages and an owner assigned to each ticket.

Before implementation: Urgency, customer potential and project value buried in conversations.

After implementation: Tags, properties and amounts that support prioritisation.

Before implementation: Limited visibility into the value of projects being handled.

After implementation: Separate views of potential projects and orders released to production.

Before implementation: Ad hoc marketing without a structured lead-quality feedback loop.

After implementation: CRM forms and events sending quality signals to Google Ads and Meta Ads.

03 / Solution architecture

One enquiry.
A clear path to an order.

We based customer handling on Help Desk in HubSpot Service Hub. Six stages structure the journey from enquiry to production order.

01 / Entering the process

An email becomes a ticket.

Messages from connected shared and individual inboxes arrive in Help Desk. Each enquiry receives its own record, and the team works from a shared queue.

The full email thread stays available, linked to the contact and company.

02 / Business rules

Check the fit first.

The team checks whether the enquiry meets the printing company’s requirements, including minimum quantities. Qualified enquiries move forward and receive a named owner.

Reply templates help the team respond efficiently to enquiries that do not meet the requirements.

03 / Ownership and context

The owner handles the enquiry in CRM.

The consultant replies from HubSpot, adds attachments and gathers missing information. The Awaiting information stage separates enquiries waiting for a customer response from those ready to progress.

Priority, category, customer potential and urgent deadlines help determine the order of work.

04 / Preparing the quote

Quoting has its own stage and value.

A qualified enquiry progresses through quoting and further discussions. The ticket amount shows the potential project value before the order is confirmed.

Email history makes it easy to revisit the assumptions behind the initial quote and subsequent agreements.

05 / Confirming the order

Won orders require complete data.

Once the order is agreed, the ticket is moved to Won (released to production). This step requires an amount and a planned production date.

Required fields provide a basis for viewing the value of work planned for the coming months.

06 / Automatic deal creation

The order enters the register.

A won ticket automatically creates a deal in HubSpot. The company gains a view of orders released to production and their value. Manufacturing continues in the external ERP.

Production and shipping statuses do not yet flow back automatically from ERP. Integration remains part of the development plan.

Current implementation scopeHubSpot structures customer service and records the handover to production. Manufacturing is managed in the existing ERP. ERP integration and automatic status updates are a planned next stage.
04 / The solution in practice

See the enquiry.
See the next step.

Defined stages organise the work of the three-person customer service team. Ticket ownership, product categories and tags help them decide what to handle next.

System views · illustrative data
01Ticket board. A shared view of status, ownership and priorities.
Full context alongside the ticket

One conversation history.
A named point of contact.

The consultant replies directly from HubSpot, adds attachments and revisits earlier agreements. Customers see the name of the person handling their enquiry, keeping communication personal.

  • Initial qualification against the printing company’s rules, including minimum quantities.
  • Reply templates for enquiries that do not meet the requirements.
  • Tags for customer potential, priority, larger orders or short deadlines.
  • Project value as another signal for prioritising work.
02Help Desk. Conversations and the details needed to handle them in one view.
From quote to order

A won order has a value.
And a planned date.

Moving a ticket to the won stage requires an amount and a planned production date. A deal is then created automatically to record the order released for fulfilment.

The company can see both the potential value of enquiries being handled and the value of confirmed work against planned dates. The deal-management part of this project used Sales Hub Starter.

A clearer basis for planning.
Order values and expected dates help the company plan ahead. Production progress, shipping status and ERP data are not yet synchronised automatically.
03Order register. Fictional order numbers and illustrative amounts.
05 / Marketing connected to service

Lead quality matters.
From acquisition to qualification.

The printing company acquires customers through Google Ads, Meta Ads and product campaigns.

We connected these activities to CRM so that information about valuable leads could flow back to the advertising platforms.

01

Campaign and form

Advertising generates an enquiry. HubSpot forms capture customer requirements and store them in CRM.

02

Assessment during handling

The team qualifies the enquiry and assesses its potential and value. Marketing gains business context for the lead.

03

Signals to ad platforms

Configured events send lead-quality signals to Google Ads and Meta Ads, supporting campaign optimisation.

A better start to the conversation

Form data is available in CRM before the consultant starts handling the enquiry. They already have most of the required information, reducing the need for initial follow-up questions.

A foundation for further optimisation

Ad account connections and conversion events are in place. More advanced attribution analysis and additional product landing pages remain part of the development plan.

06 / Implementation outcomes

Greater control.
Smoother customer service.

The implementation made the team’s work easier and customer handling faster. The key change is a clear, shared view of work from enquiry to production handover.

01 /

Clear ownership

The team can see who owns each ticket and its current stage, with a shared queue and customer conversation history.

02 /

Context-based priorities

Customer potential, project value and urgency help focus attention on the enquiries that matter most to the business.

03 /

Visibility into order value

The company can distinguish potential projects from production orders and review their value against planned dates.

04 /

A marketing feedback loop

Ad platforms receive the configured lead-quality signals, while customer service starts with the information captured in forms.

The outcomes presented here are qualitative.

The office team
works through one shared process.

HubSpot connected service, sales and marketing. The team gained shared context and the business a foundation for scaling its operations.

07 / Beyond the printing industry

A model for your process.
And your manufacturing team.

A similar setup can support a manufacturing business with up to 10 HubSpot users in its office team, covering customer service, marketing, management and operations. Suitability depends on comparable processes.

Examples include packaging, made-to-measure components, promotional materials and short-run B2B products. Suitability depends on how enquiries are handled and orders are agreed.

Technologies and implementation components
HubSpot Service HubHelp DeskHubSpot CRMSales Hub StarterHubSpot formsGoogle AdsMeta AdsEmail and automation
  • You quote projects individuallySpecifications, quantities or deadlines affect the quote.
  • You qualify enquiries before quotingMinimum quantities or other production requirements apply.
  • Several people handle customers by emailYou need a shared view, a named owner and a record of agreements.
  • You want to see order value before productionAmounts, quote status and expected dates matter.
  • You manage production in a separate systemCRM can structure customer service and order handover, with ERP integration as a next stage.

The user count refers to the office team supported by HubSpot, regardless of the size of production operations. Scope, qualification rules, forms and licences are tailored to the company’s processes; this profile is not a system limit.

08 / Further opportunities

The foundation is in place.
There is room to build on it.

The initial implementation covered customer handling through to the production order handover. Further improvements can extend that journey.

Planned development

ERP integration

Bring production and shipping updates back into HubSpot so customer service can track the order after handover.

Planned development

Complaints process

Structured handling of post-delivery issues, linked to the customer’s history.

Development direction

Landing pages and attribution

Dedicated product pages and more detailed analysis of customer acquisition sources.

Demonstrated opportunity

AI-assisted replies

For a more standardised product range: a knowledge base and draft replies for a team member to approve.

AI was not implemented in this project. With highly customised orders, the printing company chose team-led customer service. These development opportunities are separate from the outcomes described above.

Velmanta / Technology partner

Facing similar challenges?
Let's talk about your process.

Let’s explore how to structure enquiries, quoting and order handovers in your manufacturing business, using HubSpot and the tools you already work with.

Book a free consultation ↗

kontakt@velmanta.com · Explore our implementations ↗