For: Luxembourg SME founders whose revenue is growing while profit, cash, and delivery capacity feel worse
Maroun AlteklyFounder of MonyTek · Luxembourg SME consultingKey Takeaways
Margins shrink when a company sells more of the wrong kind of revenue.
The usual cause is not one bad price. It is weaker customer mix, informal discounting, hidden delivery cost, and founder attention spent on accounts that no longer fit the business.
If this is you
Revenue is up. The team is stretched. Cash is less comfortable than expected. The founder is still pulled into awkward clients. That is not a motivation problem; it is a revenue-quality problem.
Decision rule
Do not push for more pipeline until leadership can name which revenue is worth repeating.
How to use this page
Founder:Mark where you are still rescuing customers, discounts, or delivery promises.
Sales:Name which deals need exceptions before they can close and which concessions appear repeatedly.
Delivery and finance:Compare which customers are easy to serve with which customers actually fund the business.
The goal is not to create a perfect profitability model in one meeting. The goal is to make the hidden trade-offs visible enough that the next sales push, renewal conversation, or price change is based on the kind of revenue the company wants more of.
90-second diagnostic
If two or more of these signals are true, treat margin as a commercial-system issue.
Revenue is up
but cash feels tighter
The new work may be lower quality than the old work.
The team is busier
but delivery feels less repeatable
Complexity is growing faster than operational control.
Discounts feel normal
but no one can name the rule
Sales flexibility has become unmanaged margin leakage.
Large clients look attractive
but senior people keep rescuing them
Invoice size is hiding cost-to-serve.
These signals matter because they appear before the management accounts tell the full story. A founder usually feels margin erosion as noise: more exceptions, more urgent calls, more proposal revisions, more delivery complaints, and more internal meetings about accounts that should have been straightforward. The mistake is to treat each signal as a separate operational annoyance. In reality, they often point to one commercial pattern: the company is accepting revenue that does not fit the delivery model it can profitably repeat.
Margin leak map
A larger top line can hide weak pockets. The average looks acceptable while specific customers, discounts, and channels quietly damage the operating model.
Customer mix drift
More revenue from clients that need custom work, founder attention, or awkward delivery.
Which customers make the company stronger after delivery cost is counted?
Discounting without a rule
Price moves down to protect volume, but scope, timeline, or service level stays the same.
What must the customer give up or commit to when price changes?
Cost-to-serve blindness
Every customer looks equal in reporting, while delivery knows some accounts consume the team.
Which accounts would look worse if senior rescue time was visible?
Channel complexity
Cross-border or partner revenue grows, but coordination, language, compliance, or handover cost rises.
Does this channel scale the model or make it harder to control?
This is different from a pure pricing exercise. If price architecture is the main issue, use the separate guide to pricing strategy for Luxembourg SMEs. This page starts with revenue quality.
The useful leadership move is to make the leak discussable without turning it into a finance blame session. Sales may have accepted discounts because the offer was too vague. Delivery may have absorbed custom work because the proposal did not define boundaries. Finance may see weak margin only after the work has already trained customers to expect exceptions. A margin map gives the team a shared language for the operating model, not just a spreadsheet for post-mortem review.
Repair sequence
If leadership starts with blanket price increases, sales defends the pipeline. If finance starts with cost cuts, delivery protects capacity. Make revenue quality visible first.
01
Group customers by margin, repeatability, and senior attention. Do not start with industry labels if the real difference is operating burden.
02
Name who can approve a discount, when it is allowed, and what trade-off protects margin when price moves down.
03
Make the profitable segment easier to sell, onboard, renew, and serve. Margin repair is not only cost control; it is offer design.
04
Remove or redesign offers that create top-line progress and operating weakness at the same time.
The sequence also protects the team from overreacting. Not every low-margin customer should be removed. Some are strategically important because they open a market, validate a future offer, or teach the company what the next package should become. The question is whether leadership is choosing that trade-off consciously. If the team keeps making exceptions without naming the lesson, the company pays for learning but never converts it into a stronger model.
Worked example
Segment A
Fewer customers, predictable onboarding, little founder escalation, and delivery that the team can repeat without heroic effort.
Segment B
Higher deal values, more custom requests, more discount pressure, and more senior delivery time after the sale.
The answer is not to drop Segment B blindly. It may need paid discovery, stricter change control, a higher entry price, or a narrower promise. The business decision is whether the segment can be served at a margin that funds the next stage.
This is where the founder has to separate pride from economics. A large client can feel like proof that the business is moving upmarket, but the operating facts may say something different. If the client requires special reporting, special delivery sequencing, repeated senior calls, and late scope negotiation, the invoice is not the full price. The company is paying the rest in management attention and capacity.
Luxembourg lens
Luxembourg SMEs operate in a small, multilingual, cross-border market. Growth can add language, travel, compliance, partner, and delivery adaptation costs before the spreadsheet makes the burden obvious.
Usually easier trust and access, but limited market size can push custom promises.
Can expand revenue, but coordination and delivery adaptation must be priced in.
Can create reach, but ownership, handover, and accountability must stay explicit.
Guichet.lu and the Ministry of the Economy make the support landscape visible, but support does not answer the margin question. The business still has to know which work deserves investment and which work should be redesigned before it is sold harder.
This matters in Luxembourg because many SMEs grow through proximity and trust before they grow through a deliberately designed commercial system. That is a strength early on. It lets the founder adjust quickly, protect relationships, and win work that a rigid company might miss. Later, the same flexibility can become the source of margin erosion. The business needs to decide which flexibility is strategic and which flexibility is just unmanaged complexity.
Leadership checklist
If these answers are unclear, the next step is not more pipeline. It is a sales-system repair that connects customer choice, offer design, discount rules, and delivery capacity.
Can leadership name the segment with the best mix of margin, strategic fit, and delivery repeatability?
Can sales explain the discount rule without asking the founder?
Can delivery name the promises that create rework?
Can finance show rough margin by segment?
Can the company say no to revenue that makes the business weaker?
This belongs beside the repeatable sales process guide, because weak margin is often a sales-system signal before it is a finance-only issue. It also connects to customer segment selection: the right segment is not only the one that buys. It is the one the company can serve well at a margin that funds the next stage.
What not to do first
Do not launch a campaign to replace uncomfortable revenue before the model is clear. Do not ask sales to "sell higher value" without defining which buyer, which promise, and which delivery constraint. Do not automate messy work before deciding whether the work should exist in its current form. The order is diagnose, redesign, then scale.
30-minute meeting format
Keep the meeting small: founder, sales, delivery, and finance. The question is not "who is to blame for margin?" The question is "which revenue pattern should we repeat, redesign, or stop selling?"
10 min
List the customers or offers that create the most delivery exceptions. Do not debate yet. Just make the pattern visible.
10 min
Mark which of those accounts are actually strategic. A hard customer can be worth keeping if it points to the future model.
10 min
Choose one commercial rule to change: discount approval, paid discovery, scope control, renewal terms, or qualification.
Customers with clean scope, clear value, good renewal potential, and little senior rescue. Make these easier to buy and serve.
Customers with strategic value but poor delivery economics. Change scope, price, onboarding, or service level before selling more.
Revenue that consumes leadership attention, normalises discounts, or forces custom work the company does not want to become known for.
Progress signals
Margin repair should make the business calmer before it makes the spreadsheet beautiful. The first signs are usually operational: fewer exceptions, cleaner qualification, clearer renewal conversations, and less founder intervention in ordinary accounts.
Sales can explain why a deal fits before proposal work starts.
Price exceptions are visible, approved, and attached to a trade-off.
Normal accounts move forward without private founder intervention.
The team can explain what is included, what is extra, and why.
Do not judge the repair only by one month of gross margin. A single month can be distorted by billing timing, a large project milestone, or one unusual delivery issue. Judge the operating pattern. Are the right customers easier to win? Are bad-fit requests being filtered earlier? Are discounts discussed before the proposal instead of after the client objects? Is delivery learning which promises create rework? Those changes show that margin repair is becoming a management habit rather than a one-off financial review.
The strongest sign is that the company can say a precise sentence about the revenue it wants: customers who buy a defined outcome, accept a defined delivery model, renew on a defined rhythm, and do not require a known set of exceptions. That sentence becomes useful in campaigns, proposals, hiring, tooling, and pipeline reviews. Without it, margin repair stays abstract. With it, margin repair becomes commercial strategy. It also gives every team a practical filter for daily trade-offs, instead of waiting for finance to report the damage after the work is already delivered.
For Luxembourg SME policy context, see the Ministry of the Economy page on SMEs, administrative simplification, craft and retail. For support-programme context, see Guichet.lu's overview of financial aid for businesses.
These references are included for local operating context, not as proof that every SME has the same margin profile. The practical diagnosis still has to happen inside the company: by customer, by offer, by channel, and by the amount of management attention each revenue stream consumes. That is where the useful management conversation begins, because margin quality is ultimately an operating choice, not only an accounting result.
If margin shrink is coming from coordination load rather than pricing alone, check whether the company needs operations capacity visibility before adding more sales volume.