Skip to main content

Strategy - vimiBonus (Transparent Performance-Linked Bonus Distribution)

Stop deciding bonuses by feel. Use vimiClass grades + vimiGoal scores to compute a fair bonus number every month, every quarter, every year - and distribute it through vimiBank where everyone can see the math.

Note on naming. vimiBonus is a methodology - there's no separate "vimiBonus" module in the app. You run it by combining vimiClass, vimiGoal, and vimiBank. The methodology is what most successful Malaysian SMEs use to escape the "boss decides bonus by feeling" trap.

What this strategy delivers​

  • Bonus amounts that come from data, not mood
  • Staff who can predict their own bonus before the boss announces it
  • A transparent formula that survives scrutiny ("why did Wei get more than me?" → look at the grade)
  • A repeatable monthly / quarterly cycle the boss runs in 30 minutes
  • Trust - the single biggest casualty of opaque bonus systems

Why this strategy exists​

The "boss decides by feeling" bonus is the silent killer of Malaysian SME morale. I've seen it in 50+ companies. The pattern is always:

  1. Boss sits at his desk on the last day of the quarter staring at a spreadsheet of names.
  2. Tries to remember who did what well over the last 90 days.
  3. Assigns bonuses by gut feel - usually overweighting the people he saw most often (often sales staff who sit near him) and underweighting back-office (who he never sees).
  4. Announces the numbers.
  5. Half the team feels cheated. Some quit within 60 days.

The boss isn't wrong on purpose. He just can't remember 90 days of 25 staff members' performance with any precision. Memory is a terrible substitute for data.

vimiBonus fixes this by giving the formula to the system instead of to your memory.

The vimiBonus formula​

The methodology, in one diagram:

        ┌──────────────────┐
        │ vimiGoal score   │ ──┐
        │ (% of target hit)│   │
        └──────────────────┘   │
                               ├─→ Combined Performance Score
        ┌──────────────────┐   │      │
        │ vimiClass grade  │ ──┘      │
        │ (A / B / C / D)  │          │
        └──────────────────┘          ↓
                                 ┌──────────────┐
                                 │ Bonus % of   │
                                 │ base salary  │
                                 └──────────────┘
                                       │
                                       ↓
                                 ┌──────────────┐
                                 │ vimiBank     │
                                 │ payout       │
                                 └──────────────┘

You take two inputs that vimigo already calculates for you (vimiGoal completion % + vimiClass grade), combine them with a multiplier you decide once, and the system gives you a bonus number per staff per cycle. You record it in vimiBank so staff see it land.

The simplest formula (start here)​

For your first vimiBonus cycle, use this:

Bonus % = vimiClass grade × vimiGoal completion %

Where vimiClass grade maps to a multiplier:

vimiClass gradeMultiplier
A (top performer)100%
B75%
C50%
D (under-performer)25% or 0% (your choice)

And vimiGoal completion % is just the % of the target the staff hit (range 0–120% for stretch).

Worked example​

Aisha (Sales): vimiClass grade A, hit 110% of her vimiGoal target.

  • Bonus % = 100% (Class A) × 110% (goal completion) = 110%
  • Base salary: RM 4,000
  • "1 month bonus" reference = RM 4,000
  • Aisha's bonus = 110% × RM 4,000 = RM 4,400

Ahmad (Operations): vimiClass grade B, hit 90% of his vimiGoal target.

  • Bonus % = 75% (Class B) × 90% = 67.5%
  • Base salary: RM 3,200
  • Ahmad's bonus = 67.5% × RM 3,200 = RM 2,160

Wei (Customer Service, struggling): vimiClass grade D, hit 60% of target.

  • Bonus % = 25% (Class D) × 60% = 15%
  • Base salary: RM 2,800
  • Wei's bonus = 15% × RM 2,800 = RM 420

Look what just happened. Aisha (high performer) got RM 4,400. Wei (struggling) got RM 420. The 10× spread is justified by the data, not the boss's mood. If Wei asks "why did Aisha get 10× more?", you point at her grade and her goal completion. End of conversation.

How to set this up - step by step​

Step 1 - Make sure vimiClass is running with stable weights​

You can't bonus on grades that change every month. Lock your vimiClass component weights for at least 3 months before you tie real money to them.

A reasonable weighting for most SMEs:

vimiClass componentWeight
vimiGoal score (KPI hit rate)40%
Attendance (vimiCheckIn)20%
vimiReview (customer / peer review score)20%
Discretionary (boss observation, behavioural)20%

If any of these are unstable, drop them to 0 weight until stable.

Step 2 - Set the bonus reference base​

What is "1 month of bonus" in your formula? Three common options:

  • Base salary - most common. 1 month = staff's monthly base. Easy to explain.
  • Fixed RM amount - equal across all staff. "Bonus base = RM 2,000." Flatter, simpler, less hierarchical.
  • A revenue / profit share - "Bonus pool = 10% of quarterly profit, distributed proportional to bonus %." More variable, ties bonus to company performance.

Pick one. Don't change it for a year.

Step 3 - Set the multiplier table​

The example above uses 100/75/50/25. Other valid sets:

vimiClass gradeConservativeStandardAggressive
A100%100%150%
B80%75%80%
C60%50%40%
D30%25%0%

Choose based on how much you want the gap between top and bottom to widen. Conservative keeps the team flatter (good for cohesion, bad for top-performer retention). Aggressive widens the gap (good for retaining stars, may demoralise the bottom).

Step 4 - Pick the bonus cycle​

Most common in Malaysian SMEs:

  • Monthly - for sales-heavy teams or commission-style top-ups. Pairs with monthly vimiBank payout.
  • Quarterly - for most operations teams. Big enough to feel meaningful, often enough to course-correct.
  • Half-yearly - for stable teams where bonus is a retention tool, not a daily motivator.
  • Yearly - only for legacy companies. Do not start here in a new vimigo rollout.

Step 5 - Run the calculation cycle (30 minutes per cycle)​

End of cycle:

  1. Pull the vimiClass grades for the cycle.
  2. Pull the vimiGoal completion % for each staff.
  3. Apply your formula to compute bonus % per staff.
  4. Multiply by the bonus reference base (Step 2) per staff.
  5. Record each bonus into vimiBank as a payout entry - with the formula in the remarks field so staff can see the math.
  6. Pay out via your normal payroll cycle, OR through vimiBank's direct payout if you've enabled that.
  7. Announce publicly: "This cycle's bonus calculation has been done. Check your vimiBank for your number. Formula is the same as last cycle."

Step 6 - Hold a 1:1 with anyone in the bottom quartile​

This is the part most bosses skip. Don't.

For every staff in the bottom 25% of bonus payouts, schedule a 30-minute 1:1 within 7 days. Show them their grade. Show them their goal completion %. Ask one question: "What would you need from me to be in the top quartile next cycle?"

This conversation is what turns vimiBonus from a number game into a coaching tool. Bonus + 1:1 = retention. Bonus alone = transactional.

Worked example - quarterly bonus cycle for a 25-staff F&B chain​

Quarter: Q1 (Jan, Feb, Mar) Total bonus pool target: RM 50,000 (5% of quarterly revenue of RM 1M) Reference base: each staff's monthly base salary Formula: vimiClass grade × vimiGoal completion %

After running the calculation:

Staff groupCountAvg bonus
Class A, hit 100%+ goals6RM 3,200
Class B, hit 80–100% goals12RM 1,600
Class C, hit 60–80% goals5RM 800
Class D, hit under 60% goals2RM 0 (declined for the cycle)

Total payout: ≈ RM 51,000. Within budget (small over because Class A overshoot). Adjust multiplier next quarter if needed.

Of those 2 Class D staff: one took a 1:1 with the boss, agreed to a 90-day improvement plan, and was Class C+ next quarter. The other quietly resigned. Both outcomes are healthy for the company.

Common mistakes​

1. Adjusting the formula every cycle​

The whole point is predictability. If you change the multipliers every quarter because the totals "didn't feel right", you've reverted to "boss decides by feeling" with extra steps. Lock the formula for a year. Adjust during your annual review window only.

2. Bonusing on a single metric​

If you only bonus on sales (vimiGoal completion alone), you'll over-reward sales staff and under-reward back-office. Always combine with vimiClass grade so attendance, peer reviews, and behavioural factors count too.

3. No public formula​

The formula must be visible to the team. Pin it on the wall, put it in the team chat, screenshot it monthly. If staff don't know how their bonus is calculated, the system is opaque and trust dies.

4. Skipping the bottom-quartile 1:1s​

Bonus alone gives a number. Bonus + conversation gives a future. Skip the conversation and you'll lose your Class C staff to competitors who actually coach them.

5. Bonusing on data you haven't validated​

If your vimiClass grades are wrong (because component weights aren't stable), bonusing on them will create unfairness at scale. Run vimiClass for at least 3 cycles BEFORE you tie bonus to it.

Variations​

For pure-commission sales teams​

Pure commission doesn't need vimiBonus on top. The commission IS the bonus. Use vimiBonus only for non-sales staff (admin, operations, support) who don't have a natural commission formula.

For multi-branch chains​

Apply vimiBonus per-branch. Branch performance becomes an additional multiplier:

Bonus % = vimiClass grade × vimiGoal completion % × branch-performance modifier

Where branch modifier might be 1.2 (top branch), 1.0 (average), 0.8 (under-performing). This rewards both individual and branch-level performance.

For service teams without natural KPIs​

If your team can't have a numeric vimiGoal (e.g., kitchen, retail floor), use:

Bonus % = vimiClass grade × 100%

Drop the goal-completion factor. The grade alone (which includes attendance, review scores, etc.) is the bonus driver.

How vimiBonus relates to other strategies​

  • vs. Diamond × vimiRewards Day: Diamonds are for daily/weekly recognition. vimiBonus is for the big quarterly/annual money moment. Run both - they don't compete.
  • vs. Budgeting your rewards: vimiBonus IS one of your reward budget line items. It typically lives under Bucket 1 (commission / performance-tied), not Bucket 2 (committed daily motivation).
  • vs. vimiSales commission: vimiSales commission is automatic and per-deal. vimiBonus is periodic and based on aggregate performance. Use both for sales teams; use only vimiBonus for non-sales.