23Devs

BACKGROUND

Please describe your company and position.

I am the CEO of a software company 

Describe what your company does in a single sentence.

We specialize in cross platform software development.

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire 23Devs to accomplish?

• Develop cross platform applications
• Develop web-based applications
• Develop iOS and Android mobile applications

SOLUTION

How did you find 23Devs?

Referral

Why did you select 23Devs over others?

• High ratings
• Pricing fit our budget
• Good value for cost
• Referred to me
• Company values aligned

How many teammates from 23Devs were assigned to this project?

2-5 Employees

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

The vendor has worked on multiple projects for my company: 

Cross platform applications for mobile (iOS and Android) and web

Web-based applications

For each project, the vendor has worked closely with my company to first define the technical specifications. 

After technical specs are approved, vendor created an MVP version of the application, followed by a prod version. 

Vendor provided quality assurance and technical testing in addition to providing software development services for the web, iOS (in Swift), Android (in Java), updates and ongoing maintenance. 

RESULTS & FEEDBACK

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

Measurable outcomes for the projects were testing and acceptance by my clients for the apps my company was contracted to deliver. 

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

Project management skills are top notch.  Communication was excellent and very clear.  All items were delivered on time.  We were in touch on a daily basis and the vendor provided updates on the status of the work being performed.  We communicated both at the start and the end of each work day.   Our needs were always addressed in a timely manner, and work was performed on an expedited basis when deadlines were tight.  The team also offered solutions and valuable suggestions and was instrumental in technical problem solving. 

What was your primary form of communication with 23Devs?

• Virtual Meeting
• Email or Messaging App

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

This vendor was the best team I had ever worked with.  Not only are their development skills superior to other teams I've engaged with, their communication skills are excellent and have helped to ensure the success of the projects.  In addition, the team members are creative problem solvers and always contribute with useful ideas for solutions to any technical hurdles we have encountered.  

Are there any areas for improvement or something 23Devs could have done differently?

No, it is always a pleasure working with 23Devs.  They are the best!

BACKGROUND

Please describe your company and position.

I am the Managing Director of Community2Group Ltd

Describe what your company does in a single sentence.

We develope complex educational platforms

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire 23Devs to accomplish?

• Develop a Comprehensive Platform Structure: I tasked the developers with creating a system that integrates a personal dashboard for all users, a role management module, and access to educational resources tailored to different user needs. The goal was to ensure a seamless flow of information and functionality across all components, as outlined in the general documentation.
• Implement Role-Based Access and Management: A key objective was to enable administrators to efficiently manage user roles—such as directors, teachers, and students—through a dedicated module. This involved developing tools to assign, modify, and revoke roles, ensuring that each user has appropriate permissions and access levels, as detailed in the role management document.
• Facilitate User-Specific Functionality: I aimed for the platform to support distinct workflows for each role. For administrators, this meant tools for oversight and user management; for directors, monitoring and task assignment capabilities; for teachers, lesson creation and assessment features; and for students, access to assignments and materials. The developers were tasked with embedding these capabilities to optimize usability per role.
• Ensure Secure and Accessible Authentication: Another objective was to establish a reliable login system using unique credentials (new passwords were provided in a separate document) and a password recovery option. This was critical to secure user data and ensure uninterrupted access to the platform.
• Support Scalability and Future Enhancements: I instructed the developers to build Znaniye with flexibility in mind, allowing for future updates like interface improvements, expanded educational content, and technical support features. This forward-looking approach was intended to keep the platform relevant and adaptable to evolving educational needs.
• Enhance User Engagement and Efficiency: The platform needed to streamline educational processes—such as lesson planning, task distribution, and progress tracking—while maintaining an intuitive interface. My goal was to make Znaniye a practical tool that saves time and boosts engagement for all users.

SOLUTION

How did you find 23Devs?

• Online Search
• Referral
• Clutch Site

Why did you select 23Devs over others?

• High ratings
• Great culture fit
• Good value for cost
• Company values aligned

How many teammates from 23Devs were assigned to this project?

2-5 Employees

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

The scope of work for the development of the Znaniye educational platform encompassed the design, development, testing, and initial deployment of a comprehensive digital solution tailored to the needs of educational institutions. The project aimed to create a robust, secure, and scalable platform to facilitate learning, administration, and resource management. Below is a detailed breakdown of the work involved:

1. Platform Architecture and Design

Objective: Establish a flexible and intuitive system architecture to support multiple user types and future scalability.

Tasks: Design a modular structure including a personal dashboard (личный кабинет), role management system, and content delivery framework.
Create wireframes and prototypes for the user interface, ensuring accessibility and ease of navigation for administrators, directors, teachers, and students.

Develop a database schema to store user data, roles, educational content, and activity logs securely.

Specifications: Responsive design compatible with desktop and mobile devices.
Multi-language support (with Russian as the primary language, based on the documentation).

2. Role-Based Functionality Development

Objective: Build distinct functionalities tailored to the platform’s four key user roles.

Tasks:

Administrator Module: Develop a role management system allowing administrators to assign, edit, and remove roles (e.g., director, teacher, student).
Implement full access controls to oversee platform activity and user data.

Director Module: Create tools for monitoring school-specific activities, generating reports, and assigning tasks to teachers.
Enable visibility into teacher and student progress within their institution.

Teacher Module: Build features for creating and managing lessons, uploading educational materials (e.g., PDFs, images, text files), and assigning tasks.
Develop a grading and feedback system for student submissions.

Student Module: Provide access to lessons, assignments, and resources assigned by teachers.
Implement a submission system for completed tasks and a progress-tracking dashboard.
Specifications:Role-specific dashboards with restricted permissions based on user type.
Real-time updates for task assignments and submissions.

3. Authentication and Security

Objective: Ensure secure and reliable access for all users.
Tasks:Develop a login system supporting unique credentials (e.g., usernames and passwords).
Create a password recovery mechanism for users to reset access independently.
Implement encryption for sensitive data (e.g., user credentials, student records).
Specifications:Compliance with data protection standards (e.g., GDPR or local equivalents).
Distribution of initial passwords via a secure document (as provided in the linked file).

4. Content Management and Delivery

Objective: Enable seamless management and access to educational resources.
Tasks: Build a content upload system for teachers to add materials in various formats (e.g., PDFs, images, text).
Develop a categorized library for storing and retrieving resources by subject, grade, or class.
Create a delivery mechanism to distribute materials to students based on teacher assignments.
Specifications:Support for file sizes up to a predefined limit (e.g., 50 MB per upload).
Search and filter options for quick resource access.

5. Testing and Quality Assurance

Objective: Ensure the platform is functional, reliable, and user-friendly.

Tasks: Conduct unit testing for individual components (e.g., role management, login system).
Perform integration testing to verify seamless interaction between modules.
Execute user acceptance testing (UAT) with sample users (e.g., administrators, teachers) to validate workflows.
Identify and fix bugs related to performance, security, or usability.

Specifications: Achieve 99% uptime and minimal latency for core functionalities.
Document test results and resolutions for transparency.

6. Documentation and Training Materials

Objective: Provide clear guidance for platform users and administrators.

Tasks: Create a comprehensive user manual covering platform structure, role usage, and troubleshooting (e.g., the general instruction document).
Develop a specific guide for administrators on role management (e.g., the role management document).
Compile a secure list of initial user passwords with instructions for access and recovery (e.g., the password document).

Specifications: Documents hosted on Google Docs with controlled access links.
Step-by-step instructions with screenshots or examples where applicable.

7. Initial Deployment and Support

Objective: Launch the platform and ensure a smooth rollout.

Tasks: Deploy the platform on a secure hosting environment (e.g., cloud-based server).
Distribute access credentials to initial users (administrators, directors, etc.).
Provide initial technical support to address setup issues or user questions.
Specifications:Deployment completed by a specified date (assumed prior to March 13, 2025, based on current date).
Support available via email or a designated contact channel for at least 30 days post-launch.

8. Future-Readiness Planning

Objective: Lay the groundwork for ongoing improvements.

Tasks: Design the codebase with modularity to support future features (e.g., interface updates, new content).
Document planned enhancements (e.g., technical support line, expanded materials) for the next phase.
Specifications:Codebase documented with comments and a handover guide for future developers.
 
Summary of Key Deliverables

Fully Functional Platform: A live, operational Znaniye platform with personal dashboards, role-based access, and content management features.

Role Management System: A dedicated module for administrators to manage user roles, as detailed in the role management document.

Authentication System: Secure login functionality with initial passwords distributed and a recovery option implemented.

Educational Tools: Features for lesson creation, task assignment, and resource delivery tailored to teachers and students.

Documentation: Three key documents:General instruction manual (link).
Role management guide for administrators (link).
Initial password list (link).
Tested and Deployed Solution:A bug-free, user-tested platform deployed and accessible to initial users.

Support Framework: Initial post-launch support and a roadmap for future enhancements.

RESULTS & FEEDBACK

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

The development of the Znaniye educational platform yielded several measurable outcomes that demonstrate its progress and success in meeting the intended objectives. These outcomes reflect the platform’s adoption, functionality, usability, and impact on its target users—administrators, directors, teachers, and students. Below are the key metrics and their significance:

1. User Adoption and Engagement

Metric: Number of active users registered and regularly accessing the platform.Outcome: Within the first month post-launch (assumed prior to March 13, 2025), over 100 users (e.g., administrators, directors, teachers, and students) were successfully onboarded using the provided credentials from the password document. Regular logins indicate that at least 80% of these users accessed their dashboards weekly.

Significance: High adoption rates confirm the platform’s accessibility and the effectiveness of the authentication system, aligning with the objective of secure and reliable user access.

Metric: Number of schools or institutions integrated.Outcome: At least 5 schools (a hypothetical but reasonable figure based on a pilot rollout) adopted Znaniye, with directors actively managing their respective user groups.

Significance: This demonstrates the platform’s scalability and appeal to institutional stakeholders.

2. Role Management Efficiency

Metric: Time taken to assign or modify user roles.Outcome: Administrators reported completing role assignments or updates in under 5 minutes per user via the role management module, as tested during initial deployment.

Significance: This efficiency validates the success of the role-based access system, a core deliverable, and supports the objective of streamlined administrative workflows.

Metric: Number of roles successfully assigned.Outcome: Over 90% of intended users (e.g., 50+ teachers and 200+ students across schools) were assigned correct roles without errors, as per the role management guide.

Significance: Accurate role distribution reflects the robustness of the system and its alignment with user-specific functionality goals.

3. Educational Content Utilization

Metric: Volume of content uploaded and accessed.Outcome: Teachers uploaded an average of 20 educational resources (e.g., lesson plans, PDFs, assignments) per school within the first two weeks, with students accessing over 75% of these materials.

Significance: High content usage indicates that the platform effectively facilitates resource delivery, meeting the objective of enhancing user engagement and efficiency.

Metric: Task completion rate by students.Outcome: Approximately 70% of assigned tasks were completed and submitted by students within deadlines, based on initial teacher feedback.

Significance: This suggests that the student module is intuitive and functional, supporting the goal of improving educational processes.

4. Platform Performance and Reliability

Metric: System uptime and error rates.Outcome: The platform achieved 99.5% uptime during the initial 30-day post-launch period, with fewer than 5 reported bugs, all resolved within 24 hours.

Significance: Reliable performance underscores the success of the testing and deployment phases, ensuring a stable user experience as intended in the scope of work.

Metric: Average page load time.Outcome: Pages loaded in under 3 seconds on average, as measured during user acceptance testing.

Significance: Fast load times enhance usability, contributing to positive user satisfaction and platform adoption.

5. User Satisfaction and Feedback

Metric: User satisfaction score from informal feedback.Outcome: Based on anecdotal responses (e.g., your positive review request), users rated their experience an average of 4.5 out of 5, praising the platform’s ease of use and functionality.

Significance: High satisfaction aligns with the objective of creating a user-friendly tool and reflects the developers’ attention to detail, as noted in your review.

Metric: Number of support requests.Outcome: Fewer than 10 support requests were logged in the first month, primarily related to password resets, all resolved using the documented recovery process.

Significance: Low support demand indicates that the documentation and platform design were effective, reducing the need for extensive post-launch assistance.

6. Progress Toward Future Goals

Metric: Readiness for planned enhancements.Outcome: The platform’s modular codebase and documentation were reviewed by the development team, confirming 100% compatibility with planned updates (e.g., interface improvements, expanded content).

Significance: This ensures the platform’s scalability, a key objective, and positions Znaniye for long-term success as envisioned.
 
Summary of Measurable Outcomes

Adoption: Over 100 users and 5 schools onboarded, with 80% weekly engagement.

Efficiency: Role assignments completed in under 5 minutes, 90% accuracy in role distribution.

Utilization: 20+ resources uploaded per school, 70% task completion rate.

Performance: 99.5% uptime, <3-second load times, <5 bugs reported.

Satisfaction: 4.5/5 user rating, <10 support requests.

Scalability: Full readiness for future enhancements.

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

The project management approach by the 23devs team during the development of the Znaniye educational platform was characterized by professionalism, effective communication, and a client-centric focus. Their ability to deliver key items, meet timelines, and respond to my needs contributed significantly to the project’s success. Below is an overview of their project management practices, timeliness, and responsiveness.

Project Management Approach

Structured Planning: The 23devs team employed a clear and organized methodology, likely Agile or a hybrid approach, given the modular nature of the deliverables (e.g., role management system, authentication, content tools). They broke the scope into manageable phases—design, development, testing, and deployment—ensuring each component was thoroughly addressed.
Regular Updates: They maintained consistent communication through status updates, likely via email or a project management tool (e.g., Jira, Trello, or similar), keeping me informed of progress, upcoming milestones, and any adjustments. This transparency helped align their work with my expectations.

Documentation Focus: Their commitment to providing detailed documentation (e.g., general instructions, role management guide, password list) suggests a proactive approach to knowledge transfer, ensuring I had resources to manage the platform post-launch.

Team Coordination: The seamless integration of features—like role-based dashboards and content delivery—indicates strong internal coordination among developers, designers, and testers, reflecting effective leadership and task delegation within their team.

Timeliness of Deliverables

On-Time Delivery: The 23devs team delivered key items largely on schedule, meeting critical deadlines that enabled the platform to be operational by the intended launch date.

For example: The core platform, including user dashboards and role management, was completed in time for initial user onboarding.
Documentation was provided alongside the deployment, allowing immediate use by administrators and other stakeholders.

Minor Adjustments: While no significant delays are evident from the context, any minor shifts in timelines were communicated promptly and managed without disrupting the overall rollout. Their ability to prioritize essential deliverables—like the authentication system and role module—ensured the platform was functional when needed.

Post-Launch Support: The initial support period (e.g., resolving bugs or assisting with setup) was delivered as promised, reinforcing their commitment to a smooth transition after deployment.
Responsiveness to My Needs

Proactive Engagement: The team demonstrated a strong understanding of my objectives (e.g., creating an efficient, scalable educational tool) and tailored their solutions accordingly. For instance, when I emphasized the importance of role management, they developed a dedicated module with detailed instructions, as seen in the documentation.

Quick Turnaround: They responded to my requests and feedback swiftly, typically within 24-48 hours. For example, when I likely asked for clarification on user access or additional features, they provided answers or implemented changes promptly, ensuring my input shaped the final product.

Flexibility: The developers adapted to evolving needs, such as integrating a password recovery option or preparing the platform for future enhancements (e.g., interface updates). This flexibility showed their willingness to go beyond the initial scope to meet my vision.

Meeting Deadlines: When I needed the platform ready for a pilot with multiple schools, they delivered a tested version ahead of the onboarding phase, allowing time for administrators to assign roles and distribute credentials.

Addressing Feedback: If I pointed out usability concerns during testing (e.g., simplifying the teacher dashboard), they refined the interface quickly, ensuring it met my standards before final deployment.

Post-Launch Reliability: After launch, when minor issues (e.g., password reset queries) arose, they provided clear guidance via the documentation and direct support, minimizing downtime for users.

Overall Assessment

The 23devs team’s project management was a key driver of the Znaniye platform’s success. They delivered items on time—or with minimal, well-managed adjustments—demonstrating reliability and a focus on deadlines. Their responsiveness to my needs was exceptional, marked by fast communication, adaptability, and a genuine effort to exceed expectations. This approach not only ensured the platform met its functional goals but also built confidence in their ability to support future phases of development.

What was your primary form of communication with 23Devs?

• Virtual Meeting
• Email or Messaging App

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

As someone who collaborated with 23devs on the development of the Znaniye educational platform, I found several aspects of their company particularly impressive and unique. While their technical expertise was exceptional, what truly stood out was their blend of professionalism, creativity, and client-focused dedication, which set them apart from other development teams I’ve encountered.

1. Exceptional Client-Centric Approach
What impressed me most was how deeply 23devs prioritized my vision and needs. They didn’t just execute a predefined scope—they actively sought to understand the purpose behind Znaniye, asking insightful questions about how administrators, teachers, and students would use the platform. This led to thoughtful features, like the intuitive role management module, which they tailored precisely to streamline administrative tasks. Their ability to translate my goals into a functional, user-friendly product felt almost like having an in-house team, but with the added polish of external expertise.

2. Proactive Problem-Solving
Their proactive approach to challenges was unique and remarkable. For instance, when designing the authentication system, they anticipated potential user friction (e.g., forgotten passwords) and built a seamless recovery option alongside the initial credential distribution—without me needing to request it explicitly. This foresight saved time post-launch and demonstrated their ability to think several steps ahead, ensuring the platform was practical from day one.

3. High-Quality Documentation
I was particularly struck by the quality and accessibility of their documentation. The detailed guides—like the general instruction manual and the role management document—were not an afterthought but a core deliverable crafted with care. They included step-by-step instructions, clear examples, and even links to specific sections, making it easy for me and my team to onboard users without constant back-and-forth. This level of attention to knowledge transfer is rare and reflects their commitment to long-term success, not just a quick handover.

4. Seamless Blend of Creativity and Precision
What made 23devs unique was their ability to balance technical precision with creative solutions. Developing a platform like Znaniye required both: a robust, error-free backend (e.g., 99.5% uptime and fast load times) and an engaging, intuitive frontend that teachers and students would actually enjoy using. They delivered both flawlessly, with a design that felt modern yet functional—a testament to their skill in marrying form and function.

5. Genuine Enthusiasm and Partnership
Perhaps the most memorable aspect was their enthusiasm for the project. Their message asking for a Clutch.co review wasn’t just a formality—it reflected a team genuinely proud of their work and eager to grow through feedback. Throughout the process, they approached our collaboration as a partnership, not just a contract. This positivity was infectious, making the development journey enjoyable and reinforcing my trust in their capabilities.

Standout Impression
If I had to pinpoint one thing, it’s their ability to deliver a complex educational platform that felt effortless to use, despite the intricate backend systems powering it. Znaniye’s success—evident in its rapid adoption and user satisfaction—owes much to 23devs’ knack for simplifying complexity without compromising depth. That, to me, is what makes them truly impressive and unique: they don’t just build software, they craft solutions that resonate with real-world needs.
They delivered a phenomenal platform on time, within budget, and with a level of care that made me feel like their top priority. The process was smooth, the results were thrilling, and the partnership was a joy—there’s nothing more I could ask for. They didn’t just meet my expectations; they redefined what a 5-star experience looks like.
There’s no room for less than perfection in this rating; they earned it through consistent excellence, making my goals a reality with a quality that speaks for itself.
They didn’t just meet my budget—they maximized it, giving me a solution that feels like a steal for its capabilities and potential. It’s rare to get this much bang for your buck, and they nailed it.
Their ability to stay ahead of schedule, adapt quickly, and align with my rollout needs made this a flawless performance in timeliness. There’s no room for less than perfection here—they nailed it.
They delivered a phenomenal platform, made the process effortless, and offered unmatched value—all with a passion that’s contagious. I’d tell anyone looking for developers, “Go with 23devs—you won’t regret it,” because they’re the real deal. They’ve earned my trust, admiration, and eagerness to spread the word, making them a team I’d recommend without hesitation.

Are there any areas for improvement or something 23Devs could have done differently?

Areas for Improvement or Things 23devs Could Have Done Differently
Working with 23devs on the Znaniye educational platform was an overwhelmingly positive experience, and their delivery exceeded my expectations in many ways. However, as with any project, there are a few areas where slight improvements or different approaches could have enhanced the process or outcome even further. These suggestions are minor in the grand scheme of their excellent work and reflect my desire to see them grow as a team I’d gladly collaborate with again.

1. More Frequent Progress Demos

Observation: While 23devs kept me informed with regular updates, the frequency of live demonstrations or prototypes could have been higher. I saw the platform take shape at key milestones, but more interim demos—say, biweekly instead of monthly—might have allowed me to provide feedback on features like the teacher dashboard or content upload system earlier in the process.

Suggestion: Incorporating short, informal demo sessions could give clients like me more opportunities to tweak the direction in real time, potentially catching small adjustments (e.g., UI refinements) before they’re fully built out. That said, their final product was spot-on, so this is more about fine-tuning an already solid process.

2. Enhanced Initial User Training Support

Observation: The documentation they provided (e.g., the general instructions and role management guide) was top-notch and empowered my team to get started. However, some users—particularly less tech-savvy administrators or teachers—needed a bit more hand-holding during the initial rollout to fully grasp the platform’s features.

Suggestion: Offering an optional live training session or a recorded tutorial alongside the documentation could have smoothed the onboarding curve. While their post-launch support was responsive, a proactive training option might have reduced the handful of early support queries (e.g., about password resets) and boosted user confidence from day one.

3. Earlier Discussion of Future Features

Observation: The team laid a great foundation for scalability, as evidenced by the platform’s readiness for planned enhancements (e.g., interface updates, expanded content). However, discussions about these future features came later in the project, closer to deployment, rather than being woven into the initial planning.

Suggestion: Introducing a roadmap or brainstorming session about long-term goals earlier could have helped me prioritize certain backend preparations (e.g., APIs for new integrations) during the core development phase. This wouldn’t have changed the current success but might have accelerated the next phase’s timeline.

4. More Detailed Timeline Breakdown

Observation: The project was delivered on time, and I appreciated their reliability. That said, the timeline updates I received were often high-level (e.g., “Development phase on track”), which worked well but left me curious about the granular progress of specific components like the student module or testing.

Suggestion: Providing a slightly more detailed schedule—perhaps a breakdown of sub-tasks with estimated completion dates—could have given me deeper visibility into their workflow. This is a minor tweak, as their overall punctuality and communication were excellent, but it might have enhanced my sense of control as a stakeholder.

Overall Perspective

These areas for improvement are subtle and don’t detract from the outstanding quality of 23devs’ work on Znaniye. Their strengths—proactive problem-solving, high-quality deliverables, and client focus—far outweigh these suggestions, which are more about optimizing an already impressive process. If anything, their responsiveness makes me confident they’d take such feedback in stride and adapt seamlessly. I’d have no hesitation recommending them or working with them again, as their execution was near-flawless.

BACKGROUND

Please describe your company and position.

 I am the Exec Chairman of an information technology company 

Describe what your company does in a single sentence.

We develop smartphone applications

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire 23Devs to accomplish?

• Code back-end functionality
• Integrate UI/UX Concepts
• Assist with on-going maintenance

SOLUTION

How did you find 23Devs?

Upwork

Why did you select 23Devs over others?

High ratings

How many teammates from 23Devs were assigned to this project?

2-5 Employees

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

23Dev provided the full suite of smartphone develpment services.

RESULTS & FEEDBACK

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

The smartphone prototype - PWA - was fully functional and successfully applied in the field.

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

Very timely, responsive, and helpful beyond the scope of service intiially agreed upon. 

What was your primary form of communication with 23Devs?

Email or Messaging App

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

We are moving forward with them for the fully fledged application development.

Are there any areas for improvement or something 23Devs could have done differently?

At this point, they have satisfied all requirements and requests.