ZBS Tech

BACKGROUND

Please describe your company and position.

I am an Executive of Oriole Insights

Describe what your company does in a single sentence.

Oriole Insights is a crypto-related gamified prediction platform

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire ZBS Tech to accomplish?

• Design and develop the full Oriole Insights platform from scratch — including prediction markets, reputation mechanics, and gamification.
• Implement backend architecture with scalable infrastructure and real-time data tracking for crypto assets.
• Build a flexible frontend interface optimized for both web and Telegram Mini App formats.

SOLUTION

How did you find ZBS Tech?

Referral

Why did you select ZBS Tech over others?

• Close to my geographic location
• Pricing fit our budget
• Great culture fit
• Specialists in crypto

How many teammates from ZBS Tech were assigned to this project?

6-10 Employees

Describe the scope of work in detail. Please include a summary of key deliverables.

ZBS Tech built the Oriole Insights platform — a crypto prediction market and forecasting tool. The scope included full-stack development (frontend + backend), architecture planning, UX/UI implementation based on our design, and integrating gamified mechanics around predictions, reputation, and rewards.

Key deliverables included:

• Core prediction engines: UP/DOWN, ROI, Initial Listing, and Binary/Categorical Polls
• Custom reputation system based on prediction accuracy
• ORI-based voting and reward logic
• Role system, leaderboard, and user level mechanics
• Admin panel for managing markets and content
• API integration with external price feeds (CoinGecko, CMC)
• Telegram Mini App version of the platform
• Infrastructure setup (CI/CD, monitoring, deployments)
• They were involved from the MVP stage through closed and public beta, ensuring consistent delivery and iteration.

RESULTS & FEEDBACK

What were the measurable outcomes from the project that demonstrate progress or success?

ZBS Tech delivered a fully functioning MVP within 3.5 months — exactly in line with our internal roadmap. And after that - we started working on the full product development. Over 90% of features were implemented according to Figma and product specs, with design-to-code alignment checked regularly. The core backend was stress-tested to handle thousands of concurrent prediction calculations — performance exceeded expectations. Collaboration was consistent: daily standups, sprint reports, and clear accountability from their PM and tech lead.

Describe their project management. Did they deliver items on time? How did they respond to your needs?

ZBS Tech maintained consistent delivery and handled project management professionally. Weekly sprints were structured and visible in Jira, with clear ownership over tasks and transparent prioritization.

They were responsive and available daily. We had direct access to their PM and team leads, which made decision-making fast and efficient. If blockers appeared, they escalated them quickly — no radio silence, no stalling.

Most feature drops landed on time or close to deadlines. Even when specs shifted mid-sprint (as they often did), they adapted quickly without drama. Their ability to take vague ideas, clarify requirements, and turn them into implemented features was a strong point.

What was your primary form of communication with ZBS Tech?

• In-Person Meeting
• Virtual Meeting

What did you find most impressive or unique about this company?

What impressed us most was their domain expertise. The ZBS Tech team deeply understands both fintech and crypto — not just on a dev level, but also in terms of product logic, user flows, and market mechanics. Because of that, we didn’t have to waste time explaining obvious things or reworking basic features — they got it from day one.

Another huge plus: they’re just like us. Communication was fast, clear, and culturally aligned. We didn’t have to battle timezone gaps. We could speak directly, argue when needed, joke, iterate, and move forward like a real team — not like with other vendors who don’t care about your product.

Are there any areas for improvement or something ZBS Tech could have done differently?

There were a few areas where ZBS Tech could improve. While the core team was excellent, some junior developers on the backend needed tighter supervision, especially early in the project. A few bugs and rushed implementations had to be reworked by their CTO or lead devs, which slowed us down occasionally.

Also, documentation sometimes lagged behind development. We had to clarify logic manually in chats instead of just reading specs or confluence.

That said, they acknowledged these issues, fixed them fast, and adjusted the workflow. By mid-project, delivery became much smoother.