Workspace is a Split-based digital studio that designs and develops custom software and digital products. Clients choose us when they want a partner, not a vendor. We work end to end, from discovery to design, development, and delivery, then stay to support and scale. Our team builds reliable websites, web apps, and B2B platforms that fit real operations and deliver measurable results.
We focus on outcomes. In discovery we map goals, users, and workflows. In design we turn insight into clear flows, wireframes, and a reusable design system in Figma. In development we ship in small, incremental releases on a modern stack, including Next.js, React, TypeScript, Java, WordPress, Webflow, and AWS. Code quality, performance, and security are built in from day one. At delivery we train your team, monitor, and improve based on real usage.
We bring strong expertise in digital transformation for the marine and maintenance sectors, backed by our work on Serwizz CMMS. That domain knowledge helps us plan practical roadmaps, integrate with ERP and payment systems, and improve traceability on the shop floor and in the field. We also work across tourism, e-commerce, manufacturing, and professional services. Startups and SMEs trust us to move fast without cutting corners.
You get a clear plan, honest estimates, and steady releases. We align on scope early, communicate in plain language, and document every step. After launch we remain your product partner with SLA support, analytics, and a queue of improvements that keep momentum. If you need a website that converts, an internal tool that saves time, or a platform that scales, we will design and build it around your workflow.
Talk to us about your goals. We will review your needs, suggest the right approach, and outline the first steps to reach a successful release.
Workspace is a Split-based digital studio that designs and develops custom software and digital products. Clients choose us when they want a partner, not a vendor. We work end to end, from discovery to design, development, and delivery, then stay to support and scale. Our team builds reliable websites, web apps, and B2B platforms that fit real operations and deliver measurable results.
We focus on outcomes. In discovery we map goals, users, and workflows. In design we turn insight into clear flows, wireframes, and a reusable design system in Figma. In development we ship in small, incremental releases on a modern stack, including Next.js, React, TypeScript, Java, WordPress, Webflow, and AWS. Code quality, performance, and security are built in from day one. At delivery we train your team, monitor, and improve based on real usage.
We bring strong expertise in digital transformation for the marine and maintenance sectors, backed by our work on Serwizz CMMS. That domain knowledge helps us plan practical roadmaps, integrate with ERP and payment systems, and improve traceability on the shop floor and in the field. We also work across tourism, e-commerce, manufacturing, and professional services. Startups and SMEs trust us to move fast without cutting corners.
You get a clear plan, honest estimates, and steady releases. We align on scope early, communicate in plain language, and document every step. After launch we remain your product partner with SLA support, analytics, and a queue of improvements that keep momentum. If you need a website that converts, an internal tool that saves time, or a platform that scales, we will design and build it around your workflow.
Talk to us about your goals. We will review your needs, suggest the right approach, and outline the first steps to reach a successful release.
Location and contacts
Major clients
Processes and approach
How do you gather and validate client requirements?
Discovery
• Kickoff to align goals, users, and constraints
• Stakeholder interviews and a short survey
• Process mapping and pain point review
Design to clarify
• Low-fi flows and wireframes in Figma
• Clickable prototype to test key journeys
• Content and data models to remove ambiguity
• Early feasibility checks with engineering
Validation
• Stakeholder walkthroughs against acceptance criteria
• Lightweight user testing for critical paths
• Technical spikes or proofs of concept for risky parts
• Event plan for analytics to confirm success after launch
How do you ensure alignment with client goals and business strategy?
Set goals together
• Run a kickoff to map business goals, users, and constraints.
• Define what success looks like in numbers and timelines.
Show work early
• Share low-fi flows and a clickable prototype to confirm direction.
Measure and adapt
• Set up analytics, events, and dashboards that mirror the metrics.
• Review progress against targets in weekly or biweekly check-ins.
Ownership and access
• Assign a single product owner on your side and a delivery lead on ours.
• Keep a shared backlog, roadmap, and status board visible at all times.
Which software development methodologies do you use (e.g., Agile, Waterfall, Scrum)?
Primary approach
• Agile with Scrum for product builds. 1–2 week sprints, backlog grooming, sprint planning, demos, and retros.
• Kanban for support and continuous delivery. Flow-based work, WIP limits, weekly planning.
How we run it
• Dual-track: discovery and delivery in parallel.
• Clear acceptance criteria and Definition of Done.
• Small, incremental releases with CI/CD.
• Weekly or biweekly stakeholder reviews tied to metrics.
Tools
• Jira for planning and tracking.
• Figma and FigJam for design and discovery.
• GitHub, automated tests, and pipelines for releases.
How do you keep clients and stakeholders updated on project progress?
Rhythm
• Weekly summary update by email or Slack. Scope, progress, risks, next steps.
• Sprint review every 1–2 weeks with a live demo.
• Standups with your team as needed.
Live visibility
• Shared Jira board with statuses, priorities, and due dates.
• Roadmap in Jira or Notion with milestones and owners.
• Figma links for current designs and prototypes.
• CI/CD dashboard for builds, staging links, and release notes.
How frequently do you hold check-in meetings or status updates?
Standard cadence
• Weekly status update by email or Slack. Progress, risks, next steps.
• Sprint review every 1–2 weeks with a live demo.
• Optional standups 2–3 times per week with your core team.
• Monthly steering session for roadmap, scope, budget, and risks.
• Ad hoc check-ins for blockers or decisions within 24 hours.
Timing
• Work hours in CET.
• Slack replies within business hours, under 2 hours.
• Email replies same business day. Urgent issues get an immediate call.
What quality assurance practices do you follow?
Code quality
• Typed code and strict linters on every commit
• Static analysis and secret scans in CI
Manual testing
• Exploratory testing on real devices and browsers
• Regression runs before each release
CI/CD and releases
• Build, test, and scan on every push
• Staging environment with production parity
Monitoring and support
• SLA for incident response and fixes
How do you identify and manage project risks?
Identify early
• Run a risk workshop in discovery. List technical, delivery, legal, and adoption risks.
• Review assumptions, dependencies, and constraints.
Track and report
• Show changes in impact and likelihood.
• Escalate blockers within 24 hours.
Test and monitor
• Add tests for risky paths and integrations.
• Watch logs, errors, and core KPIs on staging and production.
Control change
• Log new requests with impact on scope, budget, and timeline.
• Reprioritize with you if a change adds risk.
• Lock the release scope when needed to protect the date.
What kind of support or maintenance do you offer after delivery?
Engagement models
• SLA retainer with a set number of hours
• Bucket of hours with rollover
• Fixed-scope mini releases on a schedule
Training and handover
• Team training sessions
• Admin onboarding and permission setup
• Knowledge transfer to internal teams
Coverage
• Bug fixes and hotfixes
• Security patches and dependency updates
• Performance tuning and load checks
• Uptime monitoring and alerts
• Backups and restore drills
• Content and configuration support
Enhancements
• New features and iterations
• Integrations and API changes
• UX improvements based on analytics
• A/B tests and conversion work