Team
Seventy-four specialists across eight disciplines — offices in Den Haag and Prishtina, with practice leads in Germany and Skopje. All on our own payroll. No subcontractors, no shared resource pool, no agency middle layer between you and the people doing the work.
Everything below is the method: how we design a team against your roadmap, how we hire into it, how you interview it, how we lead it — and how it becomes yours to keep after twelve months.
Leadership
No account managers. The people who scope your engagement are the people accountable for it, and they stay reachable for the length of it.
Chief Executive Officer
Runs Blocify's commercial side out of Den Haag. The first person you speak to and the one accountable for the outcome — she does not hand you to an account manager afterwards.
Managing Director
Owns the business side of every engagement: how work is scoped, priced and contracted. Sits in on the first conversation and stays reachable for the length of the relationship.
Chief Operating Officer
Accountable for velocity, quality and the weekly delivery report across all active engagements. Runs resourcing and the hiring pipeline that stands up a named squad in three weeks.
Chief Technology Officer
Owns the technical standard across every engagement and personally signs off the architecture on each new build. Runs the interview loop every engineer at Blocify has been through.
Practice leads
Practice leads run the hiring interview for their discipline, review the architecture, and sit in on your delivery reviews. They are the quality bar, in person.
Head of Design & Creativity
Runs discovery and owns the design systems our engineers build against. Ships tokens and component libraries mapped to real code, not static mockups.
Head of Mobile
Twelve apps in the stores across fintech, retail and logistics. Owns the mobile release pipeline and the device performance budgets we hold every build to.
Head of Commerce
Fifteen years in European and North American retail and B2B commerce. Has replatformed catalogues in the hundreds of thousands of SKUs without losing a season of organic traffic.
Head of Customer Experience
Runs the customer-experience operation: forecasting, rotas, coaching and the quality rubric we calibrate with every client each week.
Head of AI
Builds the evaluation suites that decide whether an AI feature ships. Allergic to demos that have never been scored against a golden dataset.
Head of Blockchain
Four mainnet launches in the last two years, zero critical findings post-launch. Writes the invariants before writing the contract.
Method
A rehearsed process, not an aspiration. Each step has an owner, a duration and an artefact you receive at the end of it.
Days 1–3
We model the team against your roadmap before we name anyone: which roles, what seniority mix, in what order, and where the single points of failure are.
Days 4–12
Candidates come from our standing bench first, then from an active pipeline in each discipline. Everyone passes the same technical gate our own engineers passed.
Days 12–16
You meet every person before they join your team, and you have the final say. We have never insisted on a placement a client was unsure about.
Days 17–21
Access, environment and security onboarding finish before day one. First production commit inside five working days, paired with a senior for the first sprint.
Ongoing
A delivery lead owns the cadence and reports weekly. Growth plans, guild reviews and bench cover keep the team stable rather than merely busy.
Month 12+
We plan the exit at kickoff. Documentation, shadowing and a formal transfer window mean the team you rely on can become the team you employ.
The bench
We keep senior specialists on the bench between engagements, paid, working on internal products. It is expensive, and it is the only reason a shortlist can exist in seventy-two hours.
The core of every product team. Strict-mode TypeScript, infrastructure as code, on-call literacy.
Cross-platform by default, native where the product depends on platform depth.
Our own floor in Prishtina — employed, trained and coached in-house across six languages.
Design that ships as tokens and components, mapped to the code your engineers write.
Eval-first delivery. Every model change is scored before it reaches a customer.
Audit-first Solidity, account abstraction and on-chain data infrastructure.
Embedded in delivery, not bolted on at the end of it.
One accountable owner per engagement. Weekly written reporting, no exceptions.
Models
2–4 specialists
5–9 specialists
5–25 agents
Scales past 20
Culture
Continuity is the cheapest way to keep quality high. Everything here exists to make staying the obvious choice for good people.
The person you interview is the person who ships. We do not rotate staff to balance our utilisation, and we do not present CVs we cannot actually deliver.
Certification, conference and learning budget carried by us. Every specialist has a growth plan reviewed quarterly, and guild time protected in the calendar.
Client teams are staffed from the same pool and to the same standard as our internal work. There is no B-team, and there are no juniors learning on your timeline.
94% of specialists are still on the same account twelve months in. Continuity is the cheapest quality mechanism there is, so we protect it contractually.
We are hiring across every discipline on this page — engineering, mobile, commerce, design, AI and the customer-experience floor in Prishtina.
Open rolesGet started
Send us the situation as it actually is. You get back a shaped engagement, a named team, a fixed timeline and a number you can put in front of a board.
A partner replies within one business day — with questions, not a sales sequence.