Scalable web applications and SaaS systems.
Product delivery grounded in clean architecture, stable implementation, and production decisions that do not collapse under growth.
Cape Town · South Africa · Est. 2021
SaaS engineering, secure design, and AI integrations with real failure handling.
NeoPendulum builds scalable web applications and AI integrations with a bias toward resilience, secure design, and production behavior that holds up when real users do unpredictable things.
Cybersecurity, testing, and failure-aware implementation.
Security thinking is treated as part of the system, alongside testing, resilience, and the way a product behaves when inputs get messy.
Robustness checks for manipulation and unsafe behavior.
Targeted pressure tests help AI-powered features resist authority pressure, urgency, identity spoofing, and similar production failure modes.
What We Build
The service mix is now tighter, more technical, and more aligned with real production work.
These services reflect the current positioning: SaaS engineering, web and UX delivery, security-minded implementation, and robustness testing for AI-enabled systems.
Secure-by-default implementation
Security review and hardening work aimed at reducing obvious attack paths, weak flows, and unsafe operational assumptions.
- Authentication and access review
- Secure design recommendations
- Failure-mode awareness
- Safer production defaults
Scalable product engineering
Multi-user systems built for growth, maintainability, and production realities rather than demo-day optimism.
- Tenant-aware application design
- Billing, roles, and admin flows
- Internal tools and dashboards
- Cloud delivery planning
Custom web builds
Fast, reliable websites and web applications that balance clear UX, solid implementation, and production performance.
- Custom front-end implementation
- API-connected web applications
- Performance-minded delivery
- Responsive production UI
Visual direction that supports conversion
Interface design that clarifies the offer, improves trust, and gives the build a coherent visual system.
- Landing page and site design
- Visual systems and hierarchy
- Component-level design thinking
- Conversion-aware page structure
UED for clearer user flows
Journey design and screen-level decision making that reduce friction and make the product easier to use under pressure.
- User-flow mapping
- Information architecture
- Wireframes and interaction logic
- Usability-oriented refinement
Release confidence through targeted testing
Testing work focused on regression risk, brittle flows, and the edge cases that usually surface after launch if nobody checks them early.
- Manual robustness checks
- Failure scenario review
- Pre-release verification
- Safer production rollouts
Foundational identity work
Logo and mark development for teams that need a cleaner visual starting point before scaling the rest of the site or product presence.
- Primary mark exploration
- Simple identity direction
- Usage-friendly asset delivery
- Visual consistency support
Research that sharpens product decisions
Structured research inputs that expose friction, clarify user priorities, and improve feature and interface direction.
- Workflow and pain-point review
- Usability observation
- Insight synthesis
- Decision support for design
Custom WordPress delivery
WordPress builds for teams that need editorial control without sacrificing visual quality or structural clarity.
- Custom page design
- Content-editing workflows
- Theme and plugin planning
- Business-ready publishing setup
SaaS Delivery
The build process is structured so products can stay reliable under load.
The focus is on scalable systems, clear interfaces, and implementation choices that still make sense once production conditions stop being friendly.
What that means in practice
We bias toward stable architecture, predictable delivery, and direct communication. The work is staged so key decisions are visible early instead of surfacing only when the system is already under pressure.
- Architecture and scope are clarified before implementation accelerates.
- Design is treated as part of product quality, not as a separate decorative layer.
- Security, testing, reporting, and admin flows are considered early.
- AI integrations are planned around real constraints and failure handling.
Typical delivery rhythm
- DiscoveryRequirements, users, and technical constraints are mapped into a realistic scope.
- Design and specificationCore journeys, interfaces, and system boundaries are aligned before build pressure rises.
- Build and reviewFeatures ship in clear slices so feedback changes the right things at the right time.
- Launch and iterateProduction release, monitoring, fixes, and next-phase work continue from a clean baseline.
Common delivery surfaces
Website front ends, SaaS dashboards, internal admin tools, WordPress builds, AI-enabled workflows, and reporting layers that need to stay understandable as they grow.
Product scoping
Admin portals
Role-based access
Billing systems
AI integrations
WordPress delivery
Security and Resilience
Systems should resist pressure, fail more safely, and behave with better operational discipline.
This is where cybersecurity, testing, and AI robustness work come together. The objective is not abstract safety language. The objective is fewer production surprises.
Secure design and failure handling
- Safer authentication, permissions, and workflow boundaries
- Design review for high-risk or brittle interaction points
- Testing around edge cases, abuse paths, and recovery behavior
- Production thinking that assumes users will do unexpected things
Focus
System resilience, secure design, and real-world failure handling rather than shallow feature polish alone.
AI robustness testing focus
- Authority pressureCheck whether the system over-complies when a request sounds senior, urgent, or high status.
- Urgency manipulationTest whether time pressure bypasses normal safety, review, or verification behavior.
- Identity spoofingProbe how the system behaves when trust signals are faked or implied rather than verified.
- Operational reviewInspect fallback behavior, boundaries, and escalation paths for unsafe or uncertain outputs.
Work Areas
Representative work across product, design, and reliability review.
These are the kinds of engagements the current service mix is built around: software delivery, interface clarity, and production-grade robustness work.
SaaS Platform
Internal operations dashboard
Multi-user web application work covering admin tooling, reporting surfaces, and flows that need to stay reliable as the system grows.
Focus: scalable implementation and clear operations visibility
Web and WordPress
Business site and content system delivery
Web design and WordPress-oriented work for teams that need editorial control, stronger structure, and a more deliberate front-end presentation.
Focus: visual clarity, maintainability, and faster publishing
Testing and AI Safety
Robustness review for AI-enabled flows
Testing work aimed at identifying manipulation risk, unsafe assumptions, and weak fallback behavior before those problems reach production users.
Focus: safer behavior under authority pressure, urgency, and spoofing attempts
Upcoming Projects
Future-facing concepts that show where product, safety, and AI work can go next.
View the first upcoming concept, EthosGuard, a marketing page for an AI ethics middleware idea focused on checking agent actions before execution.
Next Step
If the goal is a more reliable product, clearer UX, or safer AI-enabled behavior, start the conversation.
Use the contact page to book a consultation for SaaS delivery, web work, UX design, security-minded testing, or AI robustness review.