Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Picoe?
Picoe is the website of Picoe Software Solutions (also described as Curtis Wensley Consulting), a one-person software consultancy focused on computer software architecture, design and cross-platform development. The site presents it as an experienced development and technical-lead practice that builds solutions from the ground up across the full development life cycle, then maintains and enhances them after rollout.
What that means in practice
- Likely fit: teams that need architectural guidance, a cross-platform component, or an experienced developer to take a product through design, build and ongoing maintenance.
- Who it suits: smaller organizations or product teams that want a senior technical lead rather than a large agency, based on the site's emphasis on lead roles and long-term product ownership.
- Trade-off to weigh: a solo consultancy can offer direct access and continuity, but capacity for large parallel projects is limited compared with a multi-team firm.
As a next step, check the site's project or news sections for concrete examples of past work, and prepare a short brief covering your platform targets, timeline and whether you need ongoing maintenance or a one-off build. That will show quickly whether the consultancy's cross-platform and life-cycle focus matches your needs.
What software architecture and cross-platform development services does Picoe offer?
Picoe presents itself as a software architecture, design and cross-platform development consultancy, with more than 15 years of experience in development and lead technical roles. The stated offer covers building solutions from the ground up through the full development life cycle, plus maintaining and enhancing those products after rollout.
What that means in practice
The page describes capabilities rather than a fixed service menu, so the concrete work is best inferred from the stated focus:
- Architecture and design: shaping a system's structure before and during implementation, which suits teams facing a new product or a significant rewrite.
- Cross-platform development: building software intended to run across more than one platform, useful when a single codebase or consistent behaviour across environments matters.
- End-to-end delivery: involvement from initial development through implementation and rollout.
- Ongoing maintenance: continued enhancement of shipped products, which matters for organisations without in-house developers.
Who this fits
A small company that needs a desktop application working on both Windows and macOS, and has no internal architect, is the clearest match. A team that already has developers but needs design guidance at the start of a project is another. Buyers wanting a large managed team or published rate cards should look elsewhere, since the site does not set out those details.
A useful next step
Before making contact, write a one-page brief covering the platforms you need, whether the work is new build or maintenance, and the stage you are at. That lets you test whether the cross-platform and life-cycle experience described on Picoe maps onto your situation, and gives you a concrete basis for asking about comparable past projects.
How can I contact Picoe Software Solutions or Curtis Wensley Consulting to discuss a project?
Picoe Software Solutions presents itself as a software architecture, design and cross-platform development consultancy (also described as Curtis Wensley Consulting), so the natural first step for a project discussion is to use the contact route published on Picoe itself. The site does not list an email address, phone number or contact form in the supplied page information, so treat the site's own contact details as the source of truth rather than relying on third-party directories.
What to prepare before you reach out
A short, specific brief gets a faster and more useful reply:
- The problem and outcome — what the software must do and how you will judge success.
- Platforms — desktop, mobile, web or a mix, since cross-platform work is the stated specialty.
- Stage — new build from scratch, rescue of an existing product, or ongoing maintenance and enhancement.
- Constraints — timeline, existing tech stack, team members involved and any compliance needs.
- Engagement shape — architecture review, hands-on development, or a lead technical role.
Example
A small team with a working desktop tool that needs to run on macOS and Linux could send a two-paragraph note: current stack, the platforms required, the deadline, and a request for an architecture review followed by an estimate. That framing matches the services described on the site and gives the consultant enough to respond concretely.
If the published contact route goes unanswered, a professional network profile under the Curtis Wensley name is a reasonable fallback; for general due diligence, GitHub can show public repositories and activity that indicate relevant experience.
What does Picoe's track record of building software from the ground up through the full development life cycle look like?
Picoe presents its track record as end-to-end ownership of software: architecture, design, cross-platform development, and continued maintenance after rollout. The site describes more than 15 years of development and lead technical roles, and states that solutions are built from the ground up through the entire development life cycle, then maintained and enhanced after successful implementation.
What that means in practice
- Greenfield builds: Taking a product from initial architecture and design decisions through to a working, rolled-out system.
- Cross-platform work: Designing solutions that run across platforms, which usually means earlier decisions about shared code, platform-specific trade-offs, and long-term maintenance cost.
- Post-launch stewardship: The stated emphasis on maintaining and enhancing products after rollout points to ongoing involvement rather than handing off at launch.
Who this fits
A team with an idea but no existing codebase, or one whose current system needs architectural rework, is the clearest match for a from-the-ground-up engagement. A team that only needs a narrow, short-term task should check scope carefully: the site's positioning is broad lifecycle ownership, not piecework.
How to test the claim
Ask for concrete examples that map to each phase—architecture decisions, cross-platform constraints, and what maintenance looked like a year or more after rollout. The most useful signal is evidence of sustained responsibility for a product after release, since that is the part of the claim that is easiest to state and hardest to demonstrate.
As a next step, prepare a short brief of your project's platform requirements and expected post-launch support needs, and ask how Picoe would structure the architecture and maintenance phases around them.
Does Picoe provide ongoing maintenance and enhancement for products after initial rollout?
Yes. Picoe's site states that its work covers the entire development life-cycle and explicitly includes maintaining and enhancing products after successful implementation and rollout. So ongoing post-launch support is presented as part of what the firm offers, not just initial build work.
What this means in practice
- Post-rollout support: The site frames maintenance and enhancement as a continuation of the same engagement, rather than a separate handoff.
- Full life-cycle scope: Architecture, design, cross-platform development and later upkeep are described together, which suggests a single team can carry a product from concept through to later iterations.
- Experience claim: The page cites over 15 years in development and lead technical roles, plus a track record of building solutions from the ground up and then maintaining them.
Next step
If you are evaluating Picoe for a long-lived product, ask for specifics rather than relying on the general claim: typical response times, whether maintenance is retainer-based or ad hoc, how enhancement requests are prioritized, and what happens if the original developer is unavailable. Those details determine whether "ongoing maintenance" fits your operational needs.
What recent news or updates are available about Picoe's website and hosting changes?
Picoe's site announces that picoe.ca has moved to a new website hosted on GitHub Pages. The update explains that the previous site ran on a local host computer that had become outdated and could no longer be maintained, prompting the switch to GitHub Pages hosting.
What the update signals
- A platform change, not just a redesign: the move from a self-managed local server to GitHub Pages shifts hosting to a static-site service, which typically means less server maintenance for a small consultancy site.
- Continuity of the business: the same page presents Picoe Software Solutions (Curtis Wensley Consulting) as focused on software architecture, design and cross-platform development, with over 15 years of development and technical lead experience.
- No product or pricing details: the news item covers hosting and the site refresh only; it does not describe new services, releases or commercial terms.
Practical next step
If you are evaluating Picoe for a project, treat the hosting note as context rather than a capability signal. A reader comparing small consultancies might check whether a firm's site is easy to reach and whether its stated specialties match the work — for example, cross-platform architecture versus front-end-only work — and then ask directly about recent project experience. For general context on the hosting approach mentioned, see GitHub Pages.
User reviews (0)