Architecture review with ranked findings
Layered review of the PowerBuilder application: data layer, business logic, presentation, integration. Findings ranked by risk and effort, with explicit recommendations.
E · Lead
Senior Technical Leadership on PowerBuilder Systems
Architecture review, code review, project rescue and independent second-opinion consulting. Written, ranked findings — for the difficult decisions that protect a mission-critical PowerBuilder system.
- Architecture review
- Code review
- Project rescue
- Senior mentoring
What's included
Concrete deliverables in a Technical Leadership engagement
Technical leadership engagements end with documents, not slides. Each deliverable below is a written artefact you can act on independently — and circulate inside the organization.
Code review (DataWindow, .pbl structure, events)
Hands-on reading of the codebase: DataWindow design, .pbl organization, event chains, inheritance, custom controls. Specific examples flagged — not 'follow industry best practices'.
Project rescue diagnostics
Stuck project? Vendor delivering but you're unsure? We come in with no agenda and produce a written assessment: where the project actually is, what's blocking it, the realistic options.
Build and deployment pipeline review
Honest look at how the application gets from a developer's machine to production. Often a major source of risk that nobody owns. We flag what to fix first.
Test coverage assessment
Legacy PowerBuilder applications rarely have a test suite. We map what testing exists (often more than people think — DataWindow validation, business rules in events), what's missing and where to invest.
Documentation audit
What exists, what's accurate, what's missing. Often the highest-value, lowest-cost intervention: turning tacit team knowledge into written artefacts before the people leave.
Mentoring sessions for your team
Working pair-programming and review sessions with your existing developers. Not training courses — focused mentoring on the specific problems they're stuck on.
Executive-ready briefing material
4–8 page document the CTO can hand to the board: state of the system, top three risks, recommended actions, indicative cost. No marketing language.
When this engagement fits
Typical situations behind a Technical Leadership call
Leadership engagements are about clarity. They usually start when the in-house team can't decide alone, or when a decision is large enough that an independent senior view is worth the small fixed fee.
The project is stuck and stakeholders are nervous
Promised dates have slipped twice. The team is working hard but the picture inside is unclear from the outside. You need a senior outside read before the next steering committee.
We hired a junior team and need senior oversight
Cost-effective in-house team is delivering, but no one inside has the depth to spot the senior-level mistakes early. We provide that depth as part-time oversight.
Vendor is delivering — but is it any good?
External vendor or contractor is shipping code. You need an independent technical view of quality, maintainability and lock-in risk before scope expands.
Big decision ahead, need a sober second opinion
Rewrite vs modernize, on-prem vs cloud, retain vendor vs in-source. An independent senior view, in writing, costs little compared to making the wrong call.
How we work
Scope tightly, read deeply, recommend in writing
Leadership engagements work best as fixed-scope, fixed-timeline reviews. We agree the question being asked, do the work, and deliver a document that answers it.
01
Scope
What decision needs answering, by when, for whom. The clearer the question, the more useful the answer. Most reviews are 3–8 page documents, not 80-page treatises.
1 week02
Investigate
Code, architecture, team, history, build, deployment, dependencies. We read with PowerBuilder eyes — not as a generic enterprise architect would.
1–3 weeks03
Recommend
Written report with options ranked by risk and cost. We are willing to recommend one explicitly — but we document why.
1 week04
Optional follow-on
Implementation oversight, periodic re-review, pair-programming with your team. Only if the review surfaces it as the right next step.
as neededFrequently asked
Answers to common questions about PowerBuilder Technical Leadership
How is this different from regular consulting?
Regular consulting tends to deliver more time. Technical leadership engagements deliver a document and a clear recommendation, with as little time as possible. We measure success by the quality of the decision you can make after, not the hours we billed.
Will you tell our team they're doing things wrong?
Sometimes — but usually less than people fear, and always with specifics rather than judgement. We rarely meet a PowerBuilder team that isn't doing many things correctly; the value is identifying the two or three places where intervention pays back fastest.
Can you mentor our existing PowerBuilder developer?
Yes, and this is one of the highest-leverage things we do. Focused pair-programming sessions with a senior developer who shares the same idioms — much faster than generic training. Two to four hours a week, sustained for a few months, can be transformative.
What does a project rescue actually look like?
Three phases: assess (where are we really, in plain language), stabilize (stop the bleeding — pick the two changes that improve daily risk fastest), and replan (what is the realistic remaining work, with new dates). Sometimes the answer is 'cut scope'. We say it.
Do you sign engagement-specific NDAs?
Yes. For review engagements involving sensitive code or business logic, we sign your NDA before any access. Some clients prefer a mutual NDA from us — we have a standard short-form one available. References on request.
Contact
Need senior technical leadership on a PowerBuilder program?
Send a short description of the situation — what decision needs answering, what you've tried, what's blocking. We'll reply within one business day with a practical next step, usually a scoped review.
What we need first: The question you want answered, who the audience is (CIO / CTO / board / your team), and the rough timeline. The scope writes itself from there.
NDA-friendly · MSA-ready · GDPR · References on request · Hourly or fixed-fee
Other services
Adjacent engagements
Leadership reviews often produce a clear next step — sometimes modernization, sometimes database work, sometimes simply a stable support retainer. We can sequence whichever shape comes out of the review.
A · Support
PowerBuilder Legacy Support
Production support, troubleshooting, small fixes, stabilization and continuity for systems that are running but no longer easy to maintain in-house.
SLA · incident · monthly
B · EvolvePowerBuilder Modernization
Upgrade planning, PowerBuilder 2022 / 2025 readiness, UI improvements, deployment modernization, PowerServer / PowerClient strategy.
scoped · phased · safe
C · ConnectEnterprise Integrations
SAP, REST APIs, reporting systems, PDF/document workflows, external platforms — bridging PowerBuilder cleanly into the wider enterprise stack.
SAP · REST · reporting
D · DataDatabase & Performance
Oracle PL/SQL, SQL Server T-SQL, stored procedures, packages, triggers, views and performance tuning of data-heavy enterprise applications.
Oracle · SQL Server · PG
F · RetainContinuity Retainer
Reliable monthly access to rare PowerBuilder expertise without hiring a full-time developer. Reserved capacity, predictable response time.
monthly · on demand