Hedda
HR and resource planning for consultancies
Everything you know about your consultants. In one place.
Who is free in October, what an engagement earns, what the salary review will cost and how the team is doing. You already have the answers, spread across an HR system, a planning tool, the finance system and a few spreadsheets. In Hedda it all sits on the same person.
Built by a consultancy that needed it Fortnox built in Live in days Open to your AI assistant
EngagementFjordmart, until 12 October
Utilisation88 % in September, free from the 13th
Employment80% from 1 October
Leave14 days left, 5 requested for week 44
Time sheetAugust submitted, awaiting approval
Salary reviewProposal with the head of department
FeedbackFrom a client in June, from two colleagues in August
The same person in planning, time sheets, payroll and margin.
The starting point
A consultancy has one asset. The people.
Follow a question about the company far enough and you reach a person. Is she booked in November? What does he cost per hour? Who is on leave in week 44? Why did the margin on the engagement drop? Yet most consultancies get a different answer depending on which system the person asking happens to have open.
The HR system
Knows who she is and what she earns.
The planning tool
Knows where she is booked, but not what it earns.
The finance system
Knows what it earned, once the month is booked.
The spreadsheets
Know everything that did not fit anywhere else.
Every answer has a name. Hedda keeps one record per person, and every screen in the system is a view of it.
How it fits together
Change one fact. Every answer built on it follows.
Anna goes down to 80% from October
Shows less capacity to book, so nobody puts a full-time plan on her.
Expects fewer hours, and the payroll basis is right without anyone recalculating.
Her entitlement is recalculated from the same date.
Her cost per hour adjusts, so the engagement forecast is right already in October.
The same goes for a reported hour, an approved day off and a decided pay rise. They are entered once, by the person who knows, and counted everywhere they are needed. No exports, no pasting and no email to finance.
In the product
One system, wherever in the company you sit.
Consultants run their week. Managers see their team. Leadership sees the company. Nobody enters anything somebody else has already written.
AI
Your assistant can already read the company.
Hedda has a public API and an MCP server. Connect Claude, ChatGPT or whatever assistant you already use, and ask the way you would ask a colleague.
Answers come from the same staffing, time and margin you see in the system. No export that has gone stale.
A key gets exactly the rights you grant it. The assistant sees what its owner may see, and never more.
The assistant answers questions. Decisions are still made by people, in the system.
Johan Ek. The Fjordmart engagement closes on 12 October, after which he is fully available.
Priya Raman is at 60% all of October and could take on a smaller engagement alongside.
Through the MCP server, with a read key for staffing.
The alternatives
Why not something that already exists?
The PSA systems
They hold engagements and money together. The person in them is an hourly cost with a name.
The HR systems
They know everything about the person and nothing about the engagement. The margin lives somewhere else.
The enterprise suites
They do all of it, with an implementation partner, a budget to match and months before you are up and running.
The spreadsheets
Free, flexible and understood by whoever built them. Until she leaves.
Real HR and real staffing
Salary review, leave, pulse and feedback on the same person as utilisation and margin. One system, with no integration in between.
Swedish reality built in
Fortnox, pay codes, public holidays, employment rate and leave entitlement are there from the start. No configuration to teach an American system what Midsummer Eve is.
Live in days
Connect Fortnox, invite the team, start reporting. No rollout project to staff and no consultants to procure.
Built by consultants
We run a consultancy ourselves and built what we were missing. Utilisation, salary reviews and people are our everyday.
Pricing and getting started
Start without a project.
Employees and pay codes arrive exactly as they stand in payroll. Nobody types anything twice.
Everyone signs in with their work email and sees only what they are allowed to see.
Time, billing basis and margin from the same numbers. After that it is routine.
Common questions
What you want to know before booking.
Where is our data stored?
On Google Cloud in Finland, the europe-north1 region.
Do we have to replace our finance or payroll system?
No. Fortnox connects, and employees and pay codes stay in sync. Hedda handles everything that happens before the payroll run, not the payroll run itself.
Who can see salaries and margins?
Only the people you grant it to. Seeing margin and seeing salary are two separate rights, granted separately, and being a manager confers neither. The same rules apply to API keys and assistants as to people.
We already have an HR system.
Most companies do, and it is rarely opened after onboarding. Hedda is where people look every week, because staffing, time sheets and leave live there too. What the HR system knows about a person is covered, so whether to keep it is your call.
How long until we are up and running?
Days, not months. Connect Fortnox, invite the team, start reporting. There is no rollout project to staff.
Can we get our data back out?
Yes. A public API with keys you control, plus the MCP server. What you put in, you can read out, and it is your data all the way.
Everything you need to know about your consultants already exists. It just lives in too many places.
Leave your details and we'll get back to you as soon as we can to book a time. The demo runs live in Hedda, so you see how it actually works.
Thanks! We'll be in touch.
We'll reach out by email or phone to find a time that suits you.