Review of Dubb
I am finding the video tools useful, especially when the team can create a branded page and send a video by email or SMS, because the engagement figures give us something concrete to follow up on and help show whether a lead is interested; still, getting everyone set up and using it consistently is taking more patience than I would like, and I am not sure the first round feels straightforward.
The customisation is handy, but choices about branding and landing page details are falling to the implementation owner, and that can slow a busy team while we are still agreeing how video fits into ordinary follow up. Once running, real time engagement and conversion figures help decide who needs a call, which is practical, though they do not make people follow the process.
I keep coming back to this, the tools and visibility are useful, but setup and adoption have a bit of drag before things feel settled, so I am pleased overall, with some reservations.
Review of SiteSwan
Getting a client site moving looks straightforward here, with the drag and drop editor and industry templates doing much of the early work, and the business in a box approach suits an agency that needs to offer small businesses a professional website without bringing technical expertise into every job. The white label setup is useful too, since a freelancer can present the work under their own brand, domain and pricing, though I would want the handover details and access arrangements to be clear before this becomes a routine service, because that is where implementation can become fiddly.
I like that the platform is built for this kind of client work rather than only making a page, and it seems to favour speed, but templates and a simple editor do not answer every practical question about tailoring a site or managing ongoing changes, so I would check the fit against the actual client process first; still, for a small business website offer, the model feels sensible and the setup has a clear purpose.
Review of ShadowProtect
Getting image based backups into a recovery plan is taking more thought than I expected, because the software covers physical and virtual Windows servers, desktops and laptops, and I need to decide what should be protected before anyone is relying on it for each team and site. It is useful that recovery can mean a whole system, one file, or a live virtual machine, which gives our planning a practical shape. That flexibility is welcome, and the image based approach sounds sensible for reducing downtime after a serious disruption.
I am still wanting clearer confidence about permissions and the setup steps, as fast recovery only helps if the right people can act without delay. At this stage, it feels capable and dependable on paper, but the broad recovery options mean we need to think through implementation carefully, and I am not yet sure the practical handover will be as quick as the recovery itself.