Kushal's Profound AI Rep
Kushal builds systems where the architecture enforces the rules, not the application layer.
Kushal Shah
Edges
Building Multi-Tenant Permission Systems
Kushal designs permission and access control systems where the complexity of multi-tenant isolation is handled at the data model level, not patched at the application layer. At Workwise, he architected a combined RBAC and ABAC system for a hospitality procurement platform serving more than 20 hotel chains. Every role carries attribute-scoped permissions, and eligibility for approval workflows is evaluated at runtime against the business unit context. His approach is to make the wrong state structurally unreachable. Cross-tenant contamination is not prevented by a check that could be misconfigured; it is prevented by the schema itself. This pattern shows up in how he thinks about any system where multiple tenants share infrastructure: the isolation boundary belongs in the data model, and the application layer should enforce what the model already makes impossible.
Spotted in 3 Stories
Owning Complex Workflow Backends
Kushal builds backend systems for multi-stage, approval-gated workflows where the business logic is complex, the stakeholders are many, and the rules must be configurable by the operator. At Workwise, he owned the full RFQ-to-purchase-order lifecycle: vendor quoting, technical committee evaluation, commercial evaluation and negotiation, and multi-level PO approval through CFO and CEO sign-off. Each stage is gated by the permission and approval engine he designed. His instinct is to separate the workflow engine from the workflow rules. The platform defines the stages; the operator configures who acts at each stage and under what conditions. This approach produces systems that are maintainable at scale because the engineering team is not the bottleneck for every workflow change a client needs.
Spotted in 2 Stories
Adapting Architecture to Compliance Constraints
Kushal factors compliance and infrastructure requirements into architectural decisions rather than treating them as post-build constraints. At Workwise, a client's requirement for AWS infrastructure and ISO certification drove the migration from MongoDB to PostgreSQL and the implementation of end-to-end encryption across the data layer. These were not retrofits; they reshaped how the team designed storage and infrastructure going forward. He also integrated external ERP systems and AI services via REST APIs, keeping them fully decoupled from the core application state to support clients who split their operations across platforms. His approach is to treat compliance requirements as architectural inputs from the start, so the system is built to meet them rather than patched to pass them.
Spotted in 2 Stories