I turn messy ideas into polished websites, internal apps, Mendix widgets, integrations and automation flows that are useful from day one.
A premium local business site with story, structure and conversion flow.
MendixConnected
SalesforceConnected
REST APIConnected
SlackConnected
Responsive, fast and built around the next action.
Bli medlem
Your project preview
More confidence before the first conversation.
Clear offer, sharp visuals, fast loading pages and a contact path that feels obvious on every device.
Choose your build
For service businesses, clubs and founders who need a site that feels sharp, loads fast and guides visitors toward a real next step.
What I can build for you
For coaches, gyms, studios and businesses that need more leads, members and trust.
Outcome: More enquiries, more sign-ups, more confidence.Custom tools that streamline operations and help teams get real work done.
Outcome: Less friction, clearer workflows, faster decisions.Enterprise-grade apps and widgets built faster without feeling compromised.
Outcome: Reliable apps in less time.Reusable UI components and widgets that fit your product and your users.
Outcome: Better UX, less rework.APIs, webhooks and integrations that connect systems and remove silos.
Outcome: Connected data and automated flow.Practical automation and AI flows that save time and improve quality.
Outcome: Faster work, smarter decisions.Transformation diagnostic
Turn attention into enquiries.
Ask for this auditTechnical range
Sharp, responsive UI that feels designed, performs well and makes the next action obvious.
Low-code delivery with enough pro-code judgment to keep widgets, workflows and handover maintainable.
Practical integrations that connect intake, records, notifications and follow-up without manual chasing.
Rubrics, scoring loops and review surfaces that make AI-assisted work easier to trust and improve.
Recent builds and experiments
Featured live build
About the builder
I combine hands-on fullstack delivery with platform thinking: clear UX, maintainable code, Mendix-aware architecture, integrations and automation that make the work easier after launch.
Architecture showcase
A polished frontend that makes the next action obvious and keeps the system pleasant to use.
Which visitor decision should the page make easier within the first screen?
Which sections should be data-driven so the site stays easy to update?
A beautiful interface that hides the next step, repeats content or becomes painful to maintain.
Responsive routes, reusable sections, stable CTAs and copy that points to one clear action.
Component map, route notes and the first backlog of page-level improvements.
Delivery standard
Layouts get stable dimensions, mobile collapse rules and browser checks so the site still feels intentional when space is tight.
Desktop and mobile QAServices, work, skills, process, launch plan and contact options are separated from page composition so changes stay sane.
Structured content filesThe site checks the pages people can actually visit, including old paths that should keep working after the move to `/ssk`.
Smoke-tested routesREADME notes, TODOs and improvement logs make it clear what works, what is placeholder, and what should be tuned later.
Docs and TODO trailWebsites, internal tools, Mendix widgets and automation concepts are framed around data, states and follow-up work.
Architecture layersEvery major section points toward a practical decision: choose a build path, inspect work, start a sprint or write a better brief.
CTA-driven structureBefore launch
After launch ownership
Services, work proof, FAQs, contact details and repeated page copy stay in structured data where the project allows it.
Editable content mapLive pages, case studies, SSK subpages and old redirects are documented so a launch does not quietly break visitor paths.
URL and redirect notesThe build leaves behind clear surfaces like preview studios, work cards, launch panels and contact tools instead of anonymous markup.
Component inventoryTypecheck, lint, build, smoke routes and rendered QA notes make the first version easier to trust and easier to change.
Verification logTODOs and the improvement log separate placeholders from product ideas, so the next iteration starts from evidence instead of memory.
Prioritized next stepsExperience timeline
Enterprise environment
Building and improving digital solutions inside a large organization where reliability, handover and real workflows matter.
Low-code + pro-code
Working with Mendix applications, custom behavior and reusable widgets where platform speed meets frontend expectations.
Web and tools
Shipping websites, browser experiments and product surfaces with React, TypeScript and pragmatic backend thinking.
Current direction
Growing toward platform architecture by connecting systems, standardizing patterns and designing for teams who need to move faster.
Creative edge
Exploring AI evaluation, prompt quality, game mechanics and automation as a way to sharpen both product judgment and technical taste.
How we can work
Best when the offer is clear, the current site feels behind the business and the fastest win is a better first impression.
SSK Training Club shows the level of polish this can reach without turning into a heavy product build.
Best when the problem is real but still fuzzy, and the team needs something concrete enough to test with users.
The work page case studies show how interface, platform and process thinking meet in the same build.
Best when the first version exists, but quality, adoption, automation or maintainability need steady attention.
The process stays practical: clarify, prototype, build, ship and improve without losing the thread.
Scope fit
A premium first slice can clarify the offer, proof, visual system and contact path before the full site grows.
First sprint plan
We map the audience, the current friction and the one outcome the first version must prove before anything gets oversized.
One-page build briefA focused interaction, landing section, dashboard slice or Mendix widget flow becomes tangible before the whole thing is built.
Clickable or code-native prototypeThe approved slice gets production-minded code, responsive behavior, content structure and the handoff details needed to keep moving.
Shippable vertical sliceWe review what is live, what should be measured and what deserves the next sprint instead of guessing from a big abstract roadmap.
Launch notes and next-step backlogBefore the first call
Quick readiness check
Questions before we start
Not always. I look for the smallest useful move first: sharper structure, a better conversion path, one missing workflow, or a focused rebuild when the current foundation keeps fighting the goal.
Good fit when the problem is unclear trust, messy navigation or a manual workflow that keeps returning.That is a normal starting point. The first pass turns rough context into a buildable brief, a visible prototype or a small slice that makes the next decision easier.
Useful output: one-page brief, prototype direction and a practical next-step list.Yes. The sweet spot is improving platform UX around real users: custom widgets, interface patterns, API-connected flows and sharper screens that still respect the platform.
Best when a low-code app works technically but feels too clunky, generic or hard to adopt.That is part of the delivery standard. Content, routes and repeated sections should be structured so the next change is obvious instead of hidden across scattered markup.
Handover can include edit notes, TODOs, route checks and clear content locations.Yes. A focused sprint can be enough to prove the direction: one page, one tool workflow, one widget, one automation path, or one diagnostic pass before a larger build.
Small starts work best when there is one audience, one pain point and one measurable next action.We review what shipped, what needs watching and what deserves the next improvement. The goal is not just a polished first release, but a product surface that can keep getting better.
Post-launch work can cover fixes, iteration backlog, performance checks and next useful features.My process
We define the problem, users and constraints before anything gets overbuilt.
I design the core workflow quickly so direction becomes visible early.
I build clean, scalable foundations with attention to detail.
We launch, test with real users and make sure it actually works.
I iterate, optimize and evolve the product with your team.
Practical. Collaborative. Built to last.
Let's work together
Project brief
Hi Pontus, I am interested in: A conversion-focused website. Main friction: The current experience does not create enough confidence. Timeline: Soon. Context: What makes the current site, tool or workflow feel less trustworthy than it should? Useful starting point: Pontus should review the current offer, page structure, audience and strongest proof points. Best,