Founders
Who is behind Mannvit Labs.
Mannvit Labs is founded by Jonas Andersson and Johan Vartanian, who bring close to two decades of combined experience across digital marketing, e-commerce, SEO, and automation, from running their own web venture and from senior in-house roles.
They met at the University of Skövde in 2017 and co-founded Viking Web Development in 2020, running it together for four years while building content and affiliate sites and growing them through organic search. They then deepened different sides of the craft, Jonas in commercial data and e-commerce operations, Johan in technical SEO and product, before ending up at the same company again and founding Mannvit Labs.
Both founders are based in Málaga, Spain, and work remotely. Mannvit Labs is run directly by the two of them, and you can reach either of us at [email protected].
Co-founder / Systems and Delivery
Jonas Andersson
Leads systems, data, automation, and technical delivery. Works day to day in commercial data and process optimization, and previously ran e-commerce for a Swedish retailer.
LinkedIn
Co-founder / Growth and Client Development
Johan Vartanian
Leads growth, client development, and search visibility. An SEO and CRO specialist, with a background in affiliate and marketplace SEO and product management.
LinkedIn
Coverage
The problems that keep showing up.
Most of the material here comes back to the same practical failures: repetitive handling that should already be system work, handoffs that drop meaning between tools, records nobody trusts without checking manually, and exception paths that still depend on one person remembering to catch them.
Automation: repeated work that should not depend on memory.
Data visibility: records people stop trusting and the checks needed before action.
Integrations: handoffs between tools and what gets lost on the way.
Operational systems: ownership, exceptions, and release checks that keep a build usable.
Evidence ledger
What the claims here are allowed to rest on.
The site stays practice-led rather than personal-brand heavy. That makes the evidence boundary important: public builds can show approach, articles can show judgement, and private work stays private.
Commercial systems work
The perspective is grounded in direct work around commercial data, CRM records, reporting, automation, and operational handoffs.
Private employer or client systems are not shown, named, measured, or described in identifying detail.
Public builds
The public builds turn recurring operational patterns into working artifacts that can be opened, inspected, and tested.
They are independent concept builds, not client case studies or evidence of production outcomes.
Publishing discipline
The site treats publishing as system work: routes, metadata, schema, internal links, release checks, and noindex decisions are governed deliberately.
Good site hygiene supports trust, but it does not replace named client proof or identity-based trust.
Delivery standard
A useful system should make rules, owners, exceptions, failure states, and handover visible enough that someone else can operate it later.
The exact production scope depends on the real workflow, available access, data quality, and responsible owner.
Build restraint
The work starts by deciding whether the problem needs an audit, a direct build, an improvement pass, or no build at all.
Mannvit Labs does not assume automation is the answer just because automation is possible.
Point of view
Where the thinking comes from.
Commercial systems work
The perspective comes from years spent around commercial data, CRM work, reporting, automation, and the handoffs that start to fail when ownership is unclear.
Private work, public patterns
We cannot publish the private systems behind a lot of this work. Instead, we publish the repeated problems, the decisions around them, and small public builds that show how we think.
Why the name is Mannvit
Mannvit points to practical human judgement. The mark begins with Mannaz and gets rebuilt in a cleaner geometry so the human origin stays visible inside a systems shape.
Mannvit Labs is an independent systems practice and is not affiliated with Mannvit hf., COWI, or any engineering consultancy.
Public builds
Why some of the work is public.
The lab builds are independent demonstrations based on recurring operational problems. They show how we approach a problem in public, but they are not claimed as client deployments.
That lets you inspect the work without pretending private projects are public proof.
Open the build and see how the problem is modeled.
Read the related article to see the reasoning behind it.
Treat it as approach evidence, not as a case study.
About this site
What this site is for.
Mannvit Labs is a systems practice for commercial operations teams whose work depends too heavily on one person knowing how everything fits together: the report only they can finish, the CRM nobody trusts without checking, or the handoff that loses its meaning somewhere between tools.
We work around those problems in commercial systems, then publish the patterns we can show safely. The articles explain the reasoning. The builds turn some of it into public tools you can open and test.
Origin
Mannvit Labs
Systems practice
/articles
Articles
Read
Definitions, field notes, and recurring problems worth understanding properly.
/builds
Builds
Builds
Public artifacts that turn the ideas into something you can open and test.
/services
Services
Work
Audit, build, and optimisation paths for real operational problems.
/contact
Contact
Intake
Bring the workflow, report, handoff, or page that keeps causing trouble.