Scope and delivery model
Reporting periods, utilisation formula, roles and rates, mileage treatment, and service lines agreed before a single screen was built.
CoreConsult time registration
Built in the open, from brand system to live product.
This hub tracks the build as it happens: design language, delivery plan, working product, and now a live database with secure sign-in. It gives Nicolai and the team a clear way to see progress and react early.
MVP focusFast booking, live utilisation, clean reporting.
English UIDKK only37h work weekJuly-June KPI year20th-19th payslip mileageCalendar-month project reporting
Progress
Where the build stands today.
This list grows as the project moves forward, the same record that becomes the case study once we launch.
Brand system and preview hub
CoreConsult's logo, palette, type, and tone translated into a working design language, then published as this hub.
Full clickable product
Booking, project setup, dashboards, reporting, and admin controls built end to end and reviewed live with the team.
Feedback applied, twice
Two rounds of hands-on feedback shipped the same day they were raised: mobile refinements, live period-based reporting, and splitting a day's hours across multiple projects.
Live database and secure sign-in
The product now runs on its production data foundation: a real database, row-level security, and authenticated sign-in, not just mock data.
Every screen on real data
Booking, projects, reports, exports, and dashboards all read and write live data. Branded invitation emails onboard the team directly from the admin screen.
The team is in
CoreConsult consultants signed in and booking real time. Same-day fixes from their first feedback: firm-wide project view for admins and comma decimals on mobile.
Client registry and deeper reporting
Projects now draw from a managed client list instead of free text. New reporting for internal and non-client time by booking code, plus hours and revenue per consultant on every project.
Vacation reporting for payroll
A payroll-ready view of vacation in whole days per person for any period, with the dates listed and a one-click export.
Access, archiving, and per-person reporting
Consultant access now covers booking their own time, with revenue and rates kept to owners and admins. Finished projects can be archived so they leave the booking list while keeping every hour and figure in reporting. Every person-level report filters to a single individual, straight into Excel.
Design system
Quiet, structured, and fast to scan.
The interface should feel operational, not promotional. Components use CoreConsult colours and type, with restrained states for work that happens every week.
Controls
Primary action
Secondary action
StatusOn track
StatusNeeds attention
Booking card
TodayStrategy review
Client workshop prep and follow-up notes.
Metrics
Utilisation YTD78%
+4 pts vs target
Booked this week31.5h
5 client projects
Mileage period20 Jun - 19 Jul
Payslip window
Budget consumed64%
DKK 184k remaining
Alerts and notifications
Reference patterns for inline alerts, toasts, status badges, and the notification inbox. Use this section as the source of truth when adding new product feedback.
Patterns
PatternUseBehaviour
Inline alertPage-level context: incomplete week, locked period, export notesPersistent until dismissed or resolved
ToastAction feedback: saved entry, export ready, week copiedAuto-dismiss; errors stay until dismissed
Status badgeCompact state: On track, Review, UnlockedAlways visible on the row or card
Notification inboxActivity feed: exports, mileage windows, admin signalsUnread dot; mark all read
Variants
VariantLabelColourExamples
SuccessSavedThe Green BookEntry saved, export ready, week copied
InfoNoticeCommitted blueMileage period, period locked, signed out
WarningAttentionColab copperHours incomplete, budget watch, nothing to save
ErrorAction neededCaring redLocked period, blocked edit, validation failure
Keep copy short and operational. Use inline alerts for context that affects the current task. Use toasts for completed actions. Reserve error for blocked work.
Code: src/components/alerts/ · Live in app via ToastProvider on /app routes.
Inline alerts and toasts
Quiet operational feedback for saves, exports, period rules, budget risk, and locked entries. Toasts auto-dismiss; errors stay until dismissed.
AttentionWeek booking incomplete
SavedExport ready
NoticeMileage period
Action neededLocked period
Notification inbox
Lightweight activity feed for exports, mileage windows, incomplete weeks, and admin signals. Unread state only — no noisy badges elsewhere.
Inbox2 unread
Export ready2 min ago
June project summary is ready to download.
Mileage periodToday
Payslip period closes 19 July. 286 km registered so far.
Hours incompleteYesterday
5.5 hours still open against the 37-hour week.
Period lockedMon
Entries through 31 May are read-only.
Report table
ProjectService lineHoursValueStatus
Nordic growth modelStrategy84.5DKK 118kOn track
Pricing sprintCommercial Excellence42.0DKK 61kReview
PMO setupOperational Excellence56.0DKK 79kOn track
CoreGreen
#323c31Primary action, navigation, healthy status
Off-white
#e8e9e5App background and calm surfaces
Almost black
#222222Primary text and high-contrast UI
Dune
#dbd8cdPanels, separators, soft structure
Grounded sand
#9a917fMuted labels and secondary metadata
Committed blue
#415057Information and report accents
HQ blue
#8ea3aaSecondary information states
Caring red
#6b2b24Warnings and over-budget states
Colab copper
#9a5a32Warm highlight, used sparingly
The Green Book
#787458Positive supporting status
Language and tone
Professional, warm, and non-wordy.
Use
Plain labels, precise dates, calm status language, and short explanations only where they help the task.
Avoid
Marketing copy inside the app, hype, vague AI language, and long instructional text around obvious controls.
Example
“Mileage ready for payslip export. Period: 20 June to 19 July.”
AI-native delivery
Fast because the thinking is front-loaded.
The goal is not to skip planning. The goal is to make planning visible, structured, and immediately useful so build speed does not come at the cost of quality.
Context engineering first
Before building, we captured the operating rules: utilisation formula, fiscal periods, mileage windows, roles, rates, permissions, brand direction, and open decisions.
Visible thinking
The preview exposes the design language, product map, delivery sequence, and case-study path so stakeholders can react early.
Reusable system
We build the component language once, then use it across booking, project setup, dashboards, reports, admin, and exports.
Fast build loops
AI helps accelerate implementation, but quality comes from tight context, small review loops, and clear product constraints.
Human review
The client sees working surfaces quickly and can correct direction before effort builds up in the wrong place.
Launch discipline
Auth, permissions, RLS, period locking, and domain handoff are added once the core workflows are validated.
Delivery model
Context, design, build, review, iterate, launch.This is the case-study thread for Niko: AI compresses the build cycle, but the leverage comes from high-quality discovery, precise constraints, reusable components, and fast stakeholder feedback.
Brand imagery
Use real brand texture sparingly.
The product should stay focused on work. Website imagery can appear in the preview hub, onboarding, or empty states as a light brand connection, not as decoration inside dense reporting screens.
Usage ruleBrand image as context, product UI as the focus.
Keep reporting, booking, and admin screens calm. Use imagery on this preview site and occasional entry points where it supports recognition without slowing the workflow.
Delivery beats
Clear steps from context to launch.
Context and rules
Scope, reporting periods, utilisation logic, mileage treatments, service lines, and brand inputs captured before build.
Design language
A lightweight component system validates CoreConsult look, feel, tone, and operational usability before full screens are assembled.
Clickable journeys
Booking, project setup, utilisation, reporting, and exports come together as testable workflows with low-friction review links.
Secure launch
Authentication, permissions, period locking, hosting, and go-live details are finalised once the journeys feel right.
DoneDesign system and full clickable product across booking, projects, reporting, and admin
DoneProduction database, row-level security, and authenticated sign-in
DoneEvery workflow on live data: booking, projects, reporting, exports, period locking
DoneTeam onboarded with real accounts, booking real time
DoneClient registry, vacation payroll reporting, and per-person report filters
NowFirm-wide test period with same-day feedback loops
LaunchCoreConsult domain, final review, and cutover
Planning artifacts
The build is documented as it takes shape.
These are the working documents behind the preview. They capture the decisions, assumptions, and product map that let the team move quickly without losing control.
DESIGN.md
Design direction
CoreConsult palette, typography, logo rules, tone, and imagery usage.
APP_BLUEPRINT.mdApp blueprint
Sitemap, screen inventory, user stories, entities, first build sequence, and open questions.
SITEMAP.mdSitemap
Routes, navigation model, and role-aware visibility.
Brand_fundament_ Playbook.pdfBrand playbook
Source CoreConsult brand fundamentals, palette, typography, and logo rules.
Before build
Context is treated as a first-class deliverable.The app is not generated from a vague prompt. It is assembled from a visible body of context: brand rules, operational logic, sitemap, user stories, and screen planning. Sensitive commercial notes and raw client correspondence stay offline.
context/Planning and discovery artifacts├─ DESIGN.mdBrand and UI direction├─ APP_BLUEPRINT.mdScreens, user stories, entities├─ SITEMAP.mdRoutes and navigation└─ Brand playbookVisual identity sourceproduct/Built from the context├─ Design system previewComponents, states, colour, type├─ Component libraryReusable UI building blocks├─ Clickable journeysBooking, setup, reporting, admin└─ Production appAuth, data, permissions, launchCase study roadmap
How we will document the delivery story.
This same preview hub can become the retrospective: brief, context engineering, design decisions, build velocity, iteration, and final launch outcomes.
Brief
Replace imtempus plus manual Excel work with a live internal tool for time, mileage, utilisation, and reporting.
Thinking upfront
Capture rules before build: periods, service lines, roles/rates, holiday handling, permissions, and brand language.
Fast build
Once the rules are clear, assemble reusable components, product journeys, and exports quickly.
Iteration
Short review loops with visible progress: two feedback rounds already shipped the same day they were raised, not weeks later.
First working version
Choose the journey to review.
The tool is split into three role-based entry points so the client can review exactly what each type of user will see. Real row-level security decides what each person can access underneath.
Sign in, sign out, and password reset are now real: backed by a production database and secure authentication, not a mock-up. Booking, project, and reporting data is moving onto that same live foundation next.
ConsultantBook and review my time
Register time, mileage, holiday, and review personal weekly entries.
Project ownerManage projects and reportingTrack project budgets, registered value, utilisation, mileage, and reports.
AdminConfigure the operating modelReview configuration, employees, rate cards, booking codes, locks, and exports.